From: Eric Wong <normalperson@yhbt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Joakim Tjernlund <joakim.tjernlund@transmode.se>, git@vger.kernel.org
Subject: [PATCH] git-svn: understand grafts when doing dcommit
Date: Sat, 8 Sep 2007 16:33:08 -0700 [thread overview]
Message-ID: <20070908233308.GA14915@mayonaise> (raw)
In-Reply-To: <7vfy1pyluy.fsf@gitster.siamese.dyndns.org>
Use the rev-list --parents functionality to read the parents
of the commit. cat-file only shows the raw object with the
original parents and doesn't take into account grafts; so
we'll rely on rev-list machinery for the smarts here.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
---
Junio C Hamano <gitster@pobox.com> wrote:
> "Joakim Tjernlund" <joakim.tjernlund@transmode.se> writes:
>
> > hmm, I think git-cat-file is to blame.
> > git-cat-file commit da783cce390ce013b19f1d308ea6813269c6a6b5 does
> > not list list any parent...
>
> The plumbing cat-file does not deal with grafts and this is
> deliberate. Otherwise you would not be able to find the true
> set of parents when you'd want to.
>
> So do not blame cat-file, but blame the Porcelain that uses
> cat-file to read a commit object, without annotating what it
> read with what is in grafts, in this case your command line
> experiment ;-).
>
> The log family of commands and rev-list plumbing while
> traversing commit ancestry chain do take grafts into account.
>
> One caveat is pretty=raw output format shows true parents
> without grafts on "parent " header line, while the "commit "
> fake header prepended in the output for each commit shows the
> parents that takes into account.
>
> To illustrate, if you forge the history and say the parent of
> 1ddea77 is 5da1606 (when the true parent is 820eca68) with
> grafts mechanism, here is what happens:
>
> $ echo '1ddea77e449ef28d8a7c74521af21121ab01abc0 5da1606d0bf5b970fadfa0ca91618a1e871f6755' >.git/info/grafts
> $ git show -s --pretty=raw --parents 1ddea77
> commit 1ddea77e449ef28d8a7c74521af21121ab01abc0 5da1606d0bf5b970fadfa0ca91618a1e871f6755
> tree e9e61bc801438062978ff47b0963c536ed1e51a9
> parent 820eca68c2577d7499d203d7f4f7ae479b577683
> author Nick Hengeveld <nickh@reactrix.com> 1127757131 -0700
> committer Junio C Hamano <junkio@cox.net> 1127805558 -0700
>
> [PATCH] Return CURL error message when object transfer fails
>
> Return CURL error message when object transfer fails
> ...
Interesting. I didn't know about the --parents option before.
git-svn.perl | 11 +++--------
1 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index fbd4691..f818160 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -841,14 +841,9 @@ sub working_head_info {
sub read_commit_parents {
my ($parents, $c) = @_;
- my ($fh, $ctx) = command_output_pipe(qw/cat-file commit/, $c);
- while (<$fh>) {
- chomp;
- last if '';
- /^parent ($sha1)/ or next;
- push @{$parents->{$c}}, $1;
- }
- close $fh; # break the pipe
+ chomp(my $p = command_oneline(qw/rev-list --parents -1/, $c));
+ $p =~ s/^($c)\s*// or die "rev-list --parents -1 $c failed!\n";
+ @{$parents->{$c}} = split(/ /, $p);
}
sub linearize_history {
--
Eric Wong
prev parent reply other threads:[~2007-09-09 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 16:41 git-svn 1.5.3 does not understand grafts? Joakim Tjernlund
2007-09-07 16:52 ` Joakim Tjernlund
2007-09-07 20:23 ` Joakim Tjernlund
2007-09-08 5:01 ` Eric Wong
2007-09-08 11:04 ` Joakim Tjernlund
2007-09-08 17:43 ` Joakim Tjernlund
2007-09-08 19:53 ` Junio C Hamano
2007-09-08 23:33 ` Eric Wong [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070908233308.GA14915@mayonaise \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joakim.tjernlund@transmode.se \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).