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

Re: Git / Subversion Interoperability

From
DLDavid Lang <david.lang@digitalinsight.com>
Date
Mar 23, 2007, 22:05 UTC
Message-ID
<Pine.LNX.4.63.0703231357170.11744@qynat.qvtvafvgr.pbz>
In-Reply-To
<20070323193427.GA12126@c3sl.ufpr.br>
On Fri, 23 Mar 2007, Bruno Cesar Ribas wrote:
Show 23 quoted lines
> On Fri, Mar 23, 2007 at 06:13:16PM +0000, Julian Phillips wrote:
>> On Fri, 23 Mar 2007, Bruno Cesar Ribas wrote:
>>
>> Having said that, I don't think it would be a _bad_ thing if this work
>> went far enough that one could replace a Subversion server without any
>> users even noticing ;)
>
> I began to think about it... the idea to have a git-svnserver is to move from
> svn to git and get my dev team not to worry about the transition at the
> start, but it is a good idea to make people get moving to git idea of
> devlopment, right?
> Or the main idea is that we will have a group devloping under git repo and a
> group under svn-gateway for the same project? I don't see a point to have
> this! when a repo type is defined everyone must begin to understand that way,
> even if it was changed in the middle of the project.
>
> When decided above, we can define our dev of this project. Because as people
> make those 'strange' stuff at svn repo that git won't support we will have to
> make some workarounds to get git understand those things, and if we have some
> people migrated do git and some using svn they will not see some 'svn tags'
> on git repo.
>
> That's why i think it should be a transition thing from svn to git.

if you just want to transition everyone on a project from svn to git then you don't need a git-svn server, you just need a translation tool

what a git-svn server gives you is the ability to have some people use svn (becouse 'git is too complicated') while others use git.

think about sourceforge as an example. they only want to provide one version control tool, they started with cvs and are migrating to svn, but if they could put in a git server and git-svn server and support both.

think of it as 'one version control server to rule them all' (and then encourage people to do git-hg-server, git-arch-server, git-darc-server, etc)

as far as I can tell (with the exception of recording explicit renames) the git functionality is a strict superset of all the other version control tools, so it should be possible to emulate them with git. svn is just the biggest bang-for-the-buck in terms of number of users.

David Lang
Previous: Bruno Cesar RibasNext: Daniel Barkalow
Message 11 of 25 in “Git / Subversion Interoperability”
  1. Bruno Cesar RibasMar 22, 2007
  2. Shawn O. PearceMar 23, 2007
  3. Julian PhillipsMar 23, 2007
  4. Shawn O. PearceMar 23, 2007
  5. Julian PhillipsMar 23, 2007
  6. Karl HasselströmMar 23, 2007
  7. Bruno Cesar RibasMar 23, 2007
  8. Karl HasselströmMar 23, 2007
  9. Julian PhillipsMar 23, 2007
  10. Bruno Cesar RibasMar 23, 2007
  11. David LangMar 23, 2007
  12. Daniel BarkalowMar 23, 2007
  13. Shawn O. PearceMar 24, 2007
  14. Karl HasselströmMar 24, 2007
  15. Linus TorvaldsMar 24, 2007
  16. Junio C HamanoMar 24, 2007
  17. Sam VilainMar 26, 2007
  18. Christian WieseMar 23, 2007
  19. Steven GrimmMar 23, 2007
  20. Shawn O. PearceMar 24, 2007
  21. Sam VilainMar 26, 2007
  22. Jakub NarebskiMar 23, 2007
  23. Shawn O. PearceMar 24, 2007
  24. Eric WongMar 24, 2007
  25. Eric WongMar 24, 2007

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.