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

git-svn and migration

From
Nigel Magnay <nigel.magnay@gmail.com>
Date
Dec 19, 2007, 16:50 UTC
Message-ID
<320075ff0712190850r35263bcfv1d8f84e699208e15@mail.gmail.com>
In-Reply-To
<320075ff0712190849u2c40cc46pf01fa2a75f557482@mail.gmail.com>
Hi there!

I've been playing around with git for a while, read the guides to git-svn and have been successfully using it on my own to track an upstream svn repository.

Eventually, I'd like us all to switch to git, throw out the svn server, and replace it with a git repository that can be pushed to, where commits that pass tests get merged into the master.

But - that's not going to happen overnight. The most likely next steps are going to be something like migrating a couple of other developers onto git to test the water, but in the interim most people will still be on svn.

Has anyone got any tips as I'm sure it's a path trodden before? I've seen examples of keeping a read-only svn, but that's not really what I'm after. I'm considering whether to have a central git repo regularly pull from svn so that it's up to date, and having us possibly push to svn (or git if it's not merged to trunk) as an interim step..

Nigel
Next: Steven Walter
Message 1 of 5 in “git-svn and migration”
  1. Nigel MagnayDec 19, 2007
  2. Steven WalterDec 19, 2007
  3. Miklos VajnaDec 19, 2007
  4. Nigel MagnayDec 19, 2007
  5. Seth FalconDec 19, 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.