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

Re: Git-Svn-Bridge

From
Thomas Ferris Nicolaisen <tfnico@gmail.com>
Date
Nov 19, 2010, 16:30 UTC
Message-ID
<AANLkTimH=iv5y5OdBXnVM=EVY2+FvY7dTgnLc4pZSkWP@mail.gmail.com>
In-Reply-To
<227dr7-3nl.ln1@burns.bruehl.pontohonk.de>
I would like to add a +1 on this topic.

There are very few "official" resources or de-facto recipes on how to set up a git-svn bridge.

According to the 2010 survey [1], roughly 20% use git-svn in some way. A subset of these are probably very interested in a git-svn-bridge setup that works.

I've experimented with my own "hybrid bridge" setup [2], but I've yet to hear whether it's wrong or can be done better. Someone on #git claimed it was more complicated that it had to be, but as far as I've heard, the setup in Loeliger's book is even worse [3] (no offense to his book though, I haven't read it but heard it's great).

I've roamed through this mailing list, StackOverflow, and generally googled all over, but I haven't found any *really* good setups. It's not mentioned in the GitSVN migration guide [4]. With the amount of people still using git-svn, I would've thought this topic would get some more attention.

Some say that creating a centralized bridge is generally bad idea, and it's better for all to just individually use git-svn as an SVN-client directly. But I'm sure if I had advocated this at my company, checkout/update performance wouldn't impress many, and I would still be the only git-user. Thanks to the git-svn bridge, we are now a handful Git-users, using Git for builds in Hudson, and steadily gaining traction.

So, to shape it in form of a question: What is the optimal git-svn bridge setup?
Thanks,
-Thomas

[1] https://git.wiki.kernel.org/index.php/GitSurvey2010 [2] http://www.tfnico.com/presentations/git-and-subversion [3] http://blog.emmanuelbernard.com/2010/05/git-how-my-life-has-improved-since-last-month-when-i-used-svn/comment-page-1/#comment-2248 [4] https://git.wiki.kernel.org/index.php/SvnMigration

2010/11/17 Christoph Bartoschek <bartoschek@gmx.de>:
Show 29 quoted lines
> Hi,
>
> we would like to use a Git-Svn-Bridge as it is described in Jon Loeliger's
> book. However there are some open questions:
>
> We have the bridge repository and the bare repository created.
>
> a) Are the developers supposed to work on a branch that follows  master from
> the bare repository or on a branch that follows svn/trunk on the master? I
> assume they follow the master.
>
> b) How do we get changes from the bare repository to the bridge repository?
> Should there be a new branch for the changes or should one use master from
> the bridge?
>
> c) How do we get changes from subversion to the bare repository?
>
> d) Are the changes from subversion applied to the bare repository master or
> only to the svn/* branches?
>
>
> Thanks
> Christoph
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Previous: Christoph BartoschekNext: Christoph Bartoschek
Message 2 of 3 in “Git-Svn-Bridge”
  1. Christoph BartoschekNov 17, 2010
  2. Thomas Ferris NicolaisenNov 19, 2010
  3. Christoph BartoschekNov 21, 2010

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.