git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "David A. Greene" <greened@obbligato.org>
Cc: Rob Mayoff <mayoff@dqd.com>, git@vger.kernel.org
Subject: Re: [PATCH] contrib/subtree: unwrap tag refs
Date: Fri, 13 Nov 2015 00:01:24 -0500	[thread overview]
Message-ID: <20151113050123.GA29708@sigill.intra.peff.net> (raw)
In-Reply-To: <87h9kqwm67.fsf@waller.obbligato.org>

On Thu, Nov 12, 2015 at 10:36:16PM -0600, David A. Greene wrote:

> > +				sub="$(git rev-parse "$b^0")" || die "could not rev-parse split hash $b from commit $sq"
> 
> This seems like odd quoting.  Would not this do the same?
> 
> 				sub="$(git rev-parse $b^0)" || die "could not rev-parse split hash $b from commit $sq"
> 
> Perhaps I am missing something.

The former is quoting "$b" against whitespace splitting in the
sub-command. Given that the value just came from a "read" call, I think
by definition it cannot contains IFS. Still, quoting here is a good
habit.

It is actually the _outer_ quotes that are unnecessary, as variable
assignment does not do extra splitting. So:

  foo=$(echo one two)

will put the full "one two" into $foo. But the quotes do not hurt
anything, and it is a reasonable style to use them to avoid this
discussion. :)

It also matches style-wise with nearby assignments, like:

  main="$b"

-Peff

  reply	other threads:[~2015-11-13  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  4:15 [PATCH] contrib/subtree: unwrap tag refs Rob Mayoff
2015-11-13  4:36 ` David A. Greene
2015-11-13  5:01   ` Jeff King [this message]
2016-01-13  2:35   ` David A. Greene
2016-01-13 17:40     ` Junio C Hamano

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=20151113050123.GA29708@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=greened@obbligato.org \
    --cc=mayoff@dqd.com \
    /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;
as well as URLs for NNTP newsgroup(s).