From: Dan Libby <danda@osc.co.cr>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-svnimport: Use separate arguments in the pipe for git-rev-parse
Date: Thu, 20 Sep 2007 13:07:01 -0600 [thread overview]
Message-ID: <200709201307.01922.danda@osc.co.cr> (raw)
In-Reply-To: <20070918074753.GQ31176@kiste.smurf.noris.de>
Hi, it worked for the small test case. I am trying it on the large repo now,
and will let you know how it turns out. thanks!
On Tuesday 18 September 2007 01:47, Matthias Urlichs wrote:
> 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";
> --
> 1.5.2.5
--
Dan Libby
Open Source Consulting
San Jose, Costa Rica
http://osc.co.cr
phone: 011 506 223 7382
Fax: 011 506 223 7359
prev parent reply other threads:[~2007-09-20 19:29 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
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 [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=200709201307.01922.danda@osc.co.cr \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.