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 30, 2012, 12:35 UTC
Message-ID
<CALkWK0k7eCTuDdjdABpYrecf7G4_ejcsNmeCxPKSN46406U_2g@mail.gmail.com>
In-Reply-To
<4F75A571.2020304@pocock.com.au>
Hi again,
Daniel Pocock wrote:
> 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?
Yes, I think so.
> 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)

Just use contrib/svn-fe in that case: it's really quick and lightweight. You can then filter-branch the history and pull out branches by hand.

> 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)?

No corruption is possible on the Git side of things- it has cryptographic hashes for everything.

    Ram
Previous: Daniel PocockNext: dag@cray.com
Message 7 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.