git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Robert Luberda <robert@debian.org>
Cc: Eric Wong <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] git svn: handle errors and concurrent commits in dcommit
Date: Sun, 19 Aug 2012 18:20:23 -0700	[thread overview]
Message-ID: <7v393inyug.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <50316C07.30907@debian.org> (Robert Luberda's message of "Mon, 20 Aug 2012 00:43:19 +0200")

Robert Luberda <robert@debian.org> writes:

> Eric Wong wrote:
>
> Hi,
>
>> Junio C Hamano <gitster@pobox.com> wrote:
>>> I should have asked this yesterday, but do you mean you want to have
>>> your "maint" in the upcoming 1.7.12?  This does look like a useful
>>> thing to do, but does not seem like a regression fix to me.
>> 
>> Yeah, I wasn't sure what to name it since my master is still carrying
>> Michael's larger SVN 1.7 changes.   Perhaps I should've named my "maint"
>> "for-git-master" in this case...
>
>
> While working on my next patch, I've accidentally discovered that bash gives
> the following errors in the test file introduced in my commit :
>
> ./t9164-git-svn-dcommit-concrrent.sh: line 65: $hook: ambiguous redirect
> ./t9164-git-svn-dcommit-concrrent.sh: line 66: $hook: ambiguous redirect

Thanks.  It is this one (especially the latter half "Note that")
in the Documentation/CodingGuidelines.

 - Redirection operators should be written with space before, but no
   space after them.  In other words, write 'echo test >"$file"'
   instead of 'echo test> $file' or 'echo test > $file'.  Note that
   even though it is not required by POSIX to double-quote the
   redirection target in a variable (as shown above), our code does so
   because some versions of bash issue a warning without the quotes.

  reply	other threads:[~2012-08-20  1:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 21:26 [PATCH/RFC] git svn: handle errors and concurrent commits in dcommit Robert Luberda
2012-08-02 10:44 ` Eric Wong
2012-08-08  5:32   ` Robert Luberda
2012-08-08  5:35     ` Robert Luberda
2012-08-08 23:07     ` Eric Wong
2012-08-09 17:44       ` Junio C Hamano
2012-08-10 19:51         ` Eric Wong
2012-08-19 22:43           ` Robert Luberda
2012-08-20  1:20             ` Junio C Hamano [this message]
2012-08-21 22:01             ` Eric Wong
2012-08-24 23:47               ` Robert Luberda
2012-08-26  0:34                 ` Eric Wong
2012-08-31  6:29                   ` [PATCH] t9164: More style fixes Robert Luberda
2012-08-31 18:01                     ` 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=7v393inyug.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    --cc=robert@debian.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;
as well as URLs for NNTP newsgroup(s).