If you haven't used git-svn here are the two posts that helped me most:
If you want a more full-fledged git hosting setup, you can use gitosis: http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way
I already had my subversion tree checked out via git, but it was up-to-date and because each git-svn checkout creates it's own set of revisions to represent the repository, I just started from scratch. Also, HTTP doesn't seem useful as a central repository for an in-house group like mine because you're going to be pushing back to the repository, so didn't even bother setting it up. I know you can setup push over HTTP, but I heard working over ssh is faster. By the way, make sure you're using 1.5 or higher, anything less just doesn't cut it.
- I created a directory called /var/git and did a git-svn checkout of the subversion repository from the same server in there:
- mkdir myproj
- cd myproj
- git svn init -s file:///path/to/repo
- Then I created the public git repository: (from the Git user manual)
- cd ../
- git clone --bare myproj myproj.git
- cd myproj.git
- git --bare update-server-info
- chmod a+x hooks/post-update
You'll need to make sure you have public key ssh authentication setup for everyone using git. We already did so I didn't have to go through that. Also, if you don't trust your developers on the server, you can use set their shell to 'git-shell' which is a restricted shell that only allows git commands.
1 comment:
In case you still care, git's grafts feature would have probably done what you needed.
I've posted on this in the context of git-svn based conversions, and David Wheeler has an interesting example from his Bricolage conversion.
Post a Comment