git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: Dan Libby <danda@osc.co.cr>, git@vger.kernel.org
Subject: Re: [PATCH] git-svnimport: Use separate arguments in the pipe for git-rev-parse
Date: Tue, 18 Sep 2007 01:54:01 -0700	[thread overview]
Message-ID: <7vlkb4wdzq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070918074753.GQ31176@kiste.smurf.noris.de> (Matthias Urlichs's message of "Tue, 18 Sep 2007 09:47:53 +0200")

Matthias Urlichs <smurf@smurf.noris.de> writes:

> Signed-Off-By: Matthias Urlichs <smurf@smurf.noris.de>
> ---
> Please tell me whether that works for you.
>
> Somebody else, preferably its author, can fix git-svn. ;-)
> 
> diff --git a/git-svnimport.perl b/git-svnimport.perl
> index d3ad5b9..aa5b3b2 100755
> --- a/git-svnimport.perl
> +++ b/git-svnimport.perl
> @@ -633,7 +633,7 @@ sub commit {
>  
>  	my $rev;
>  	if($revision > $opt_s and defined $parent) {
> -		open(H,"git-rev-parse --verify $parent |");
> +		open(H,'-|',"git-rev-parse","--verify",$parent);
>  		$rev = <H>;
>  		close(H) or do {
>  			print STDERR "$revision: cannot find commit '$parent'!\n";

I seem to be missing the context, but please describe what
problem this fixes in the commit log message.  I guess some
people use shell metacharacters and/or SP in their branch names
and this is about that problem?

  reply	other threads:[~2007-09-18  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200709161857.06065.danda@osc.co.cr>
     [not found] ` <20070917070303.GI31176@kiste.smurf.noris.de>
     [not found]   ` <200709171333.48331.danda@osc.co.cr>
2007-09-18  7:47     ` [PATCH] git-svnimport: Use separate arguments in the pipe for git-rev-parse Matthias Urlichs
2007-09-18  8:54       ` Junio C Hamano [this message]
2007-09-18  9:29         ` Matthias Urlichs
2007-09-20 19:40           ` Dan Libby
2007-09-21  6:11             ` Matthias Urlichs
2007-09-21  6:59               ` Junio C Hamano
2007-09-21 10:24                 ` Matthias Urlichs
2007-09-21 20:21                   ` Dan Libby
2007-09-20 19:07       ` Dan Libby

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=7vlkb4wdzq.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=danda@osc.co.cr \
    --cc=git@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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).