git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] cvsimport: always pass user data to "system" as a list
Date: Wed, 30 Apr 2008 08:30:42 +0100	[thread overview]
Message-ID: <320075ff0804300030q227cee39w28bfb8456a97995f@mail.gmail.com> (raw)
In-Reply-To: <20080430043614.GA31019@sigill.intra.peff.net>

This fixed my import problem - thanks for the swift identification (my
perl isn't so hot so it scared me :) )

On Wed, Apr 30, 2008 at 5:36 AM, Jeff King <peff@peff.net> wrote:
> This avoids invoking the shell. Not only is it faster, but
>  it prevents the possibility of interpreting our arguments in
>  the shell.
>
>  Signed-off-by: Jeff King <peff@peff.net>
>  ---
>  Nigel reported a problem with a CVS branch that had '(' in the name. No
>  report yet on whether this fixes it, but it should be done regardless.
>
>  I checked over git-cvsimport.perl, and this was the only instance I
>  found.
>
>   git-cvsimport.perl |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
>  diff --git a/git-cvsimport.perl b/git-cvsimport.perl
>  index 95c5eec..bdac5d5 100755
>  --- a/git-cvsimport.perl
>  +++ b/git-cvsimport.perl
>  @@ -772,7 +772,7 @@ sub commit {
>         waitpid($pid,0);
>         die "Error running git-commit-tree: $?\n" if $?;
>
>  -       system("git-update-ref $remote/$branch $cid") == 0
>  +       system('git-update-ref', "$remote/$branch", $cid) == 0
>                 or die "Cannot write branch $branch for update: $!\n";
>
>         if ($tag) {
>  --
>  1.5.5.1.178.gc1eb9.dirty
>
>

      reply	other threads:[~2008-04-30  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  4:36 [PATCH] cvsimport: always pass user data to "system" as a list Jeff King
2008-04-30  7:30 ` Nigel Magnay [this message]

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=320075ff0804300030q227cee39w28bfb8456a97995f@mail.gmail.com \
    --to=nigel.magnay@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).