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

git-svn and sharing a single subversion repo to multiple clients

From
DFDuncan Ferguson <duncan_j_ferguson@yahoo.co.uk>
Date
Feb 12, 2010, 08:13 UTC
Message-ID
<838B8633-E2B2-4833-BE09-5DCE9A13BBE1@yahoo.co.uk>
Hiya list,
The git-svn man page has a section on setting up a single git-svn repository and sharing it out so multiple clients can then clone it (in the section in 'BASIC EXAMPLES', starting at "The initial git-svn clone can be quite time-consuming ....").
I have tried following this but it does not work for me on 1.6.3.3
My situation is my company has a subversion repository that takes a significant amount of time to git-svn clone (many hours) due to the length of time its been used.  I work across a number of dev servers all using the same single subversion repo and dev servers are semi-regularly rebuilt.  I'd like to check out the subversion repo once on a 'stable' server and then git clone it to all the dev servers to speed up creating a new dev server (and reduce disk space), but also be able to pull any new subversion commits and also push new commits back.
What is the best/correct way of setting this up as I cannot find any other docs apart from the section in the git-svn man page that doesn't work?
Thanks
  Duncs
Next: Duncan Ferguson
Message 1 of 2 in “git-svn and sharing a single subversion repo to multiple clients”
  1. Duncan FergusonFeb 12, 2010
  2. Duncan FergusonFeb 18, 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.