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

git-svn: how to connect SVN branches?

From
Ddherring@ll.mit.edu <dherring@ll.mit.edu>
Date
Jan 17, 2008, 20:17 UTC
Message-ID
<alpine.LNX.0.999999.0801171237110.3479@mojave>
Hi,

The project I'm tracking changed servers a couple months ago. To simulate the svn-switch, I edited the svn-remote.url to the new location. `git-svn fetch`, `git-svn dcommit`, and the like seemed to work ok.

When a new release branch came out, I tried adding svn-remote.branches = releases/*:refs/remotes/svn/*

`git-svn fetch` pulled the new branch. However, it created a whole new history for this branch (new git commits from the beginning of the SVN repo).

Is there some way to tell git/git-svn to connect these two histories?
Pictorially, I have

SVN1@a---SVN2@a---SVN3@b---SVN4@b---SVNtrunk SVN1@b---SVN2@b---SVN3@b---SVN4@b---SVNbranch

and want
SVN1@a---SVN2@a---SVN3@b---SVN4@b---SVNtrunk
                                  \--SVNbranch

Similarly, if someone cloned a git repo full of git-svn-id's (which indicate that an svn --switch occurred) but without any matching git-svn data, is there a way to `git-svn fetch` from the new SVN repo and autoconnect the git commits?

Thanks, Daniel

Next: Sam Vilain
Message 1 of 4 in “git-svn: how to connect SVN branches?”
  1. dherring@ll.mit.eduJan 17, 2008
  2. Sam VilainJan 17, 2008
  3. dherring@ll.mit.eduJan 18, 2008
  4. Gregory JefferisJan 17, 2008

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.