mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] consolidate command line escaping
Date: Mon, 30 Jan 2006 22:49:08 +0100	[thread overview]
Message-ID: <20060130214908.GA28626@mars.ravnborg.org> (raw)
In-Reply-To: <43DDE4AB.76F0.0078.0@novell.com>

On Mon, Jan 30, 2006 at 10:04:27AM +0100, Jan Beulich wrote:
> From: Jan Beulich <jbeulich@novell.com>
> 
> While the recent change to also escape # symbols when storing C-file
> compilation command lines was helpful, it should be in effect for all
> command lines, as much as the dollar escaping should be in effect for
> C-source compilation commands. Additionally, for better readability and
> maintenance, consolidating all the escaping (single quotes, dollars,
> and now sharps) was also desirable.

Very nice paths - thanks!
I have applied it locally and will commit if it when testing a bit more.

> -cmd = @$(if $($(quiet)cmd_$(1)),\
> -      echo '  $(call escsq,$($(quiet)cmd_$(1)))' &&) $(cmd_$(1))
> +cmd = @$(echo-cmd) $(cmd_$(1))
Here you replace 
	echo 'xxx' && cmd
with
	echo 'xxx'; cmd

Since we assume echo will always succeed I see no difference in
behaviour, but I recall the '&&' was there for some specific reason.
Just wondering why it is so - I see no problems with it.

	Sam

  reply	other threads:[~2006-01-30 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30  9:04 Jan Beulich
2006-01-30 21:49 ` Sam Ravnborg [this message]
2006-01-31  8:03 Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060130214908.GA28626@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=JBeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome