Best Practice for following Subversion repository Trunk: Git (Mirror), Git-Svn, Subversion?

Answer 1

If you're not going to be making changes to the Django code, then there's no reason to import it into Git. Just use option 1.

Using git-svn (either by running it yourself or by cloning somebody else's repository) is useful if you want to make local modifications to a project that uses Subversion (whether or not you send any of those modifications back to the project). But if you're not making any local modifications, then it's just needless complexity.

Answer 2

I agree with @cjm. If you just want a copy of the Django sources, use plain Subversion.

My experience with git-svn is that it is most useful for people who prefer and are more familiar with Git who have to track a Subversion-repository, and not so useful to people who are know Subversion but are git-newbies wanting something better than Subversion. There are several limitations to git-svn stemming from the fact that Subversion has inferior merge tracking, and unless you have some substantial git experience those limitations will jump up and bite you at times.

Answer 3

Well, if you are using git for all your projects and you are reasonably familiar with it I would suggest to use the git mirror, as it seams to be reasonably up to date. Git should also be faster than using Subversion. If the mirror goes away / gets outdated you can always just svn co / svn up to get the current source.

But as you also have Subversion installed - you could also just use it instead ... doesn't make a big difference and is more a question of personal preference.

Git-svn is a little more tedious to setup and keep in sync - you have to fetch the subversion updates first using git svn fetch and then doing a git svn rebase to apply the changes to the git repository. It will also use up more disc space. This is somewhat more error-prone and I would only recommend using git-svn if you actually wanted to do development on the source tree. If you feel adventurous and want to give it a try have a look at this Tutorial - i found it quite useful to get going with git-svn.