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

Re: git-svn fetch

From
doki_pen <doki_pen@doki-pen.org>
Date
May 29, 2009, 20:31 UTC
Message-ID
<4A20460B.8030709@doki-pen.org>
In-Reply-To
<4A20090F.3070608@drmicha.warpmail.net>
Michael J Gruber wrote:
> Doki Pen venit, vidit, dixit 29.05.2009 17:09:
>   
[snip]
>> The problem I'm experiencing is that everytime a new branch is added, 
>> git svn fetch seems to download the entire history all the way from r1. 
[snip]
Show 12 quoted lines
>
> AFAIK git-svn has to go back in order to search for possible earlier
> history of $newbranch. For git-svn, the following two scenarios are
> basically equivalent:
>
> - a new branch is added to the svn repo
> - you change your git-svn config so that a new branch becomes
> "interesting" (which had been skipped before)
>
> git-svn treats them the same way ("a branch we don't know about yet"),
> because it can't really (reliably) distinguish between them.
>   

Turns out that in their infinite wisdom, the repo gods laid out the structure like this:

/trunk
  /Source
     [THECODE]
  /SomethingElse
  /SomeOtherStuff
/branches
  /BRANCH-1
     [THECODE]
  /...

The problem was I had trunk set to /trunk and not /trunk/Source. This was a bad mistake. Since I have fixed it git-svn is quite a bit faster!

TY
Previous: Michael J Gruber
Message 3 of 3 in “git-svn fetch”
  1. Doki PenMay 29, 2009
  2. Michael J GruberMay 29, 2009
  3. doki_penMay 29, 2009

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.