Re: git-svn: cloning an SVN repo with sub-branches and sub-tags
- From
- Daniel Pocock <daniel@pocock.com.au>
- Date
- Mar 30, 2012, 12:22 UTC
- Message-ID
- <4F75A571.2020304@pocock.com.au>
- In-Reply-To
- <CALkWK0mn=vWexhYMNPV5iKf-hX5gTHYjOS4o+E1mFjUtL49hmg@mail.gmail.com>
On 29/03/2012 16:32, Ramkumar Ramachandra wrote:
Show 34 quoted lines
> Hi Daniel, > > Daniel Pocock wrote: >> git svn clone \ >> -T trunk \ >> -t tags \ >> -b branches \ >> https://flactag.svn.sourceforge.net/svnroot/flactag \ >> flactag-git1 >> >> I don't get any of the branches or tags, and I get numerous warnings like >> this: >> >> W: -empty_dir: branches/d_pocock/autotools/HTTPFetch.cc >> W: -empty_dir: branches/d_pocock/autotools/HTTPFetch.h >> W: Cannot find common ancestor between >> f475b655c10b55b36df8376a396c0d9534418617 and >> 7e277bfd626a1caa84681e93a7af73e0160eb2eb. Ignoring merge info. >> W: Cannot find common ancestor between >> f475b655c10b55b36df8376a396c0d9534418617 and >> a82cd9bd2197a89303558af9aad43fa0c23d1ddb. Ignoring merge info. > > These look like genuine warnings; git-svn probably doesn't like your > repository (nested branches/ tags, missing mergeinfo etc) > >> I have the impression that git-svn does not like the repository layout, and >> it is not clear from the manual page how to make it work. Can anyone share >> any advice about this? > > Off the top of my head, you could try doing two things: > 1. Try exporting the branches and tags by hand one-by-one. > 2. You could try using reposurgeon [1] to fix the repository. > > [1]: http://esr.ibiblio.org/?p=4071
The flactag project is not something of a commercial nature, so we were really looking at quick solutions
One other factor I didn't mention in the original email, some of the branches have been renamed/moved within the SVN repo - is that a problem for git-svn?
One compromise I have thought about would be just extracting trunk, and forgetting about the branches, and manually tagging the official releases (as there were very few of them, this is quick)
However, based on the errors/warnings, is it possible that there is any corruption in the gitified version of trunk (or the history of trunk)?