Re: git-svn pulling down duplicate revisions

[Kevin Ballard <kevin@sb.org>]

On Jun 1, 2008, at 10:00 PM, Eric Wong wrote:

> Kevin Ballard <kevin@sb.org> wrote:
>> 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.

The repository is, unfortunately, a private repo so I can't share it.  
I used `git svn clone -s` to clone it. I have the SVN perl bindings  
v1.4.4 (according to git svn --version).

I definitely have read permissions to the repo root. If I specify to  
only fetch -r 12000:HEAD (there's 14000-odd revisions), it doesn't  
pull down any duplicates, but when I let it start from the root, it  
pulls down hundreds of duplicates for multiple branches.

-Kevin Ballard

-- 
Kevin Ballard
http://kevin.sb.org
kevin@sb.org
http://www.tildesoft.com