threads / discuss / 22623

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

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

## tl;dr

2 messages between Feb 12, 2010 and Feb 18, 2010.

replies: 1people: 1as markdown or json

Duncan Ferguson· Feb 12, 2010, 08:13 UTC · lore
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
Duncan Ferguson· Feb 18, 2010, 11:35 UTC · re: Duncan Ferguson · lore

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

On 12 Feb 2010, at 08:13, Duncan Ferguson wrote:
Show 8 quoted lines
> 
> 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?
For anyone else looking to do this I found some details on the wiki at: http://git.wiki.kernel.org/index.php/GitFaq#How_do_I_mirror_a_SVN_repository_to_git.3F - the wiki was being moved when i first asked so I didn't find it then - and it appears to be struggling now...
  Duncs

← back to recent threads