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
Dave Zarzycki <zarzycki@apple.com>
Date
Mar 30, 2012, 16:20 UTC
Message-ID
<A3CEE238-4A0F-4335-BC81-BB90885938BF@apple.com>
In-Reply-To
<4F75A413.409@pocock.com.au>
On Mar 30, 2012, at 5:16 AM, Daniel Pocock <daniel@pocock.com.au> wrote:
Show 10 quoted lines
> On 29/03/2012 15:40, Dave Zarzycki wrote:
>> You can make this work, but it is very fragile, doesn't scale well, and it only works on recent versions of git. For example, from the LLVM clang project:
> 
> ...
> 
>> branches = cfe/branches/Apple/*:refs/remotes/svn/misc/Apple/*
>> branches = cfe/branches/Apple/Necropolis/*:refs/remotes/svn/misc/AppleNecropolis/*
> 
> 
> In the first line, (Apple/*), can it accidentally think that Necropolis is a branch, when it actually appears to be a directory containing branches?
Correct.
> Or does it consider all the lines in the file together?
It does not. That is why the "ignore-refs" setting is necessary. The "ignore-refs" setting tells git that "Necropolis" etc are not valid branches (because they are SVN subdirectories). The "ignore-refs" setting is useful for working around other SVN user errors too.
davez
Previous: Daniel PocockNext: Ramkumar Ramachandra
Message 4 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.