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

Re: git-svn: cloning an SVN repo with sub-branches and sub-tags

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Mar 29, 2012, 15:32 UTC
Message-ID
<CALkWK0mn=vWexhYMNPV5iKf-hX5gTHYjOS4o+E1mFjUtL49hmg@mail.gmail.com>
In-Reply-To
<4F7467E1.3090004@pocock.com.au>
Hi Daniel,
Daniel Pocock wrote:
Show 18 quoted lines
> 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
    Ram
Previous: Dave ZarzyckiNext: Daniel Pocock
Message 5 of 9 in “git-svn: cloning an SVN repo with sub-branches and sub-tags”
  1. Daniel PocockMar 29, 2012
  2. Dave ZarzyckiMar 29, 2012
  3. Daniel PocockMar 30, 2012
  4. Dave ZarzyckiMar 30, 2012
  5. Ramkumar RamachandraMar 29, 2012
  6. Daniel PocockMar 30, 2012
  7. Ramkumar RamachandraMar 30, 2012
  8. dag@cray.comMar 29, 2012
  9. Stephen BashMar 29, 2012

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.