git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: differences between old clone and new Re: git-svn performance

From
EWEric Wong <normalperson@yhbt.net>
Date
Oct 28, 2014, 07:41 UTC
Message-ID
<20141028074104.GA7762@dcvr.yhbt.net>
In-Reply-To
<1414474807.30075.YahooMailBasic@web172303.mail.ir2.yahoo.com>
Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
Show 16 quoted lines
> 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.
Previous: Hin-Tak LeungNext: Hin-Tak Leung
Message 3 of 14 in “Re: Anomaly with the new code - Re: git-svn performance”
  1. Hin-Tak LeungOct 27, 2014
  2. differences between old clone and new Re: git-svn performanceHin-Tak Leung, Oct 28, 2014
  3. Eric WongOct 28, 2014
  4. Hin-Tak LeungOct 28, 2014
  5. Eric WongOct 30, 2014
  6. Hin-Tak LeungOct 30, 2014
  7. Eric WongOct 30, 2014
  8. Regression and failure to clone/fetch with new code Re: git-svn performanceHin-Tak Leung, Oct 28, 2014
  9. Eric WongOct 29, 2014
  10. Hin-Tak LeungOct 30, 2014
  11. Eric WongOct 30, 2014
  12. Hin-Tak LeungOct 30, 2014
  13. Eric WongOct 30, 2014
  14. Eric WongOct 28, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.