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

Re: git-svn pulling down duplicate revisions

From
EWEric Wong <normalperson@yhbt.net>
Date
Jun 2, 2008, 05:00 UTC
Message-ID
<20080602050050.GC9904@hand.yhbt.net>
In-Reply-To
<1AD7D1A1-EC3B-450D-A648-04ADB8180E46@sb.org>
Kevin Ballard <kevin@sb.org> wrote:
Show 8 quoted lines
> I started a git-svn clone on a large svn repository, and I noticed  
> that for various branches, it kept pulling down the exact same  
> revisions (starting at r1). In other words, if I had 4 branches that  
> shared common history, their common history all got pulled down 4  
> times. I double-checked, and the created commit objects were identical.
> 
> Why was git-svn pulling down the same revisions over and over, when it  
> already knows it has a commit object for those revisions?

Can you give me an example if a repository and command-line you used that does this? Did you use 'git svn clone -s' or did you manually specify the branch locations in the repo?

It could even be a lack of read permissions to the repository root that would cause things like this.

Thanks,
-- 
Eric Wong
Previous: Kevin BallardNext: Kevin Ballard
Message 2 of 8 in “git-svn pulling down duplicate revisions”
  1. Kevin BallardMay 20, 2008
  2. Eric WongJun 2, 2008
  3. Kevin BallardJun 2, 2008
  4. Eric WongJun 2, 2008
  5. Kevin BallardJun 2, 2008
  6. Eric WongJun 2, 2008
  7. Kevin BallardJun 2, 2008
  8. Björn SteinbrinkJun 2, 2008

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.