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

Re: git svn fetches the same revision multiple times for non-trunk branches

From
Robert Zeh <robert.a.zeh@gmail.com>
Date
Jul 27, 2009, 23:56 UTC
Message-ID
<E9365F62-FD6F-4770-B177-9B8F0413C12C@gmail.com>
In-Reply-To
<20090725105111.GB13534@dcvr.yhbt.net>

So is the basic problem that the history of the branch is unknown and we have to retrieve the history?

Robert On Jul 25, 2009, at 5:51 AM, Eric Wong wrote:

Show 26 quoted lines
> Robert Zeh <robert.a.zeh@gmail.com> wrote:
>> I am seeing git svn fetch repeatedly retrieve the same Subversion
>> revisions when it finds branches in our Subversion repository. We are
>> using the standard Subversion repository layout, with top level / 
>> trunk,
>> /tags, and /branches directories (and the git repository was  
>> created with
>> 'git svn init -s'). However, the problematic branches are often  
>> copies
>> made from a subdirectory inside of trunk, instead of trunk.
>
> Hi Robert,
>
> Yes, this is a known problem with some repositories and there's no
> automatic/easy[1] way to handle it with globbing tags/* or branches/*.
>
> You can try to track each tagged project independently or to setup
> individual fetche lines (like the one generated for trunk).  in
> .git/config for each tag/branch.
>
> [1] - Unfortunately SVN allows way too much freedom and thus ambiguity
> in how it treats tags/branches and that doesn't allow mapping those
> things to git very easily.
>
> -- 
> Eric Wong
Previous: Eric WongNext: Eric Wong
Message 3 of 4 in “git svn fetches the same revision multiple times for non-trunk branches”
  1. Robert ZehJul 24, 2009
  2. Eric WongJul 25, 2009
  3. Robert ZehJul 27, 2009
  4. Eric WongJul 28, 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.