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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]