From: Eric Wong <normalperson@yhbt.net>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: stoklund@2pi.dk, fabian.schmied@gmail.com, git@vger.kernel.org,
sam@vilain.net, stevenrwalter@gmail.com, waste.manager@gmx.de,
amyrick@apple.com
Subject: Re: differences between old clone and new Re: git-svn performance
Date: Tue, 28 Oct 2014 07:41:04 +0000 [thread overview]
Message-ID: <20141028074104.GA7762@dcvr.yhbt.net> (raw)
In-Reply-To: <1414474807.30075.YahooMailBasic@web172303.mail.ir2.yahoo.com>
Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> To compare the old clone with the new, I did:
>
> git branch -r | sort | xargs -n 1 git log --decorate=full -n 1
>
> It turned out other than the empty vs 3 word commit messages
> about two years ago on trunk (which are inherited in all the newer
> branches), there are two other groups of differences.
>
> One branch on the old clone has an extra merge from trunk (
> and some extra trunk commits) listed in 'git log', while
> another branch has the exact opposite - on the old clone
> has one fewer merge.
>
> I see the merge seem to be genuine - the subversion log
> often says so e.g. "ported from rXXX from trunk", but
> the extra/missing pattern isn't consistent.
So both merges are correct, but we lose one, and gain one?
I'll try to check more closely tomorrow. Can you point out
the exact revisions in the R repo? Thanks.
> So the histories are largely the same, except due to the
> extra merge, don't have the same sha1 sums.
next prev parent reply other threads:[~2014-10-28 7:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 23:26 Anomaly with the new code - Re: git-svn performance Hin-Tak Leung
2014-10-28 5:40 ` differences between old clone and new " Hin-Tak Leung
2014-10-28 7:41 ` Eric Wong [this message]
2014-10-28 23:59 ` Hin-Tak Leung
2014-10-30 0:21 ` Eric Wong
2014-10-30 0:55 ` Hin-Tak Leung
2014-10-30 23:08 ` Eric Wong
2014-10-28 23:33 ` Regression and failure to clone/fetch with new code " Hin-Tak Leung
2014-10-29 19:23 ` Eric Wong
2014-10-30 0:06 ` Hin-Tak Leung
2014-10-30 0:28 ` Eric Wong
2014-10-30 2:35 ` Hin-Tak Leung
2014-10-30 8:46 ` Eric Wong
2014-10-28 7:45 ` Anomaly with the new code - " Eric Wong
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=20141028074104.GA7762@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=amyrick@apple.com \
--cc=fabian.schmied@gmail.com \
--cc=git@vger.kernel.org \
--cc=htl10@users.sourceforge.net \
--cc=sam@vilain.net \
--cc=stevenrwalter@gmail.com \
--cc=stoklund@2pi.dk \
--cc=waste.manager@gmx.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).