I've migrated out Subversion repository to Git. You can see it at https://sourceforge.net/u/ncjones/pytrainer/. All history and tags have been preserved.
If we are happy with the state of this repository then we can move it over to the Pytrainer project and stop using Subversion. To migrate the Pytrainer Svn repository to Git I basically just followed the instructions at http://stackoverflow.com/questions/79165. Here's the exact steps I took: 1. created users.txt containing names/email addresses of all committers: azapletal david dgranda ilovesquigly jblance jliljenfeldt kevindication lubos moe_bius ncjones siggipals vud1 2. ran git-svn migration on the repository and waited an hour or so: $ git svn clone --stdlayout --no-metadata -A users.txt https://pytrainer.svn.sourceforge.net/svnroot/pytrainer pytrainer-git-migration 3. grafted the "beta" branch back into master to preserve history as per http://stackoverflow.com/questions/8157647. The grafted revisions were: 196 (first commit to beta branch) onto 192 (trunk state before beta branch) and 286 (first commit on trunk after merging beta branch) onto 280 (last commit on beta branch) 4. grafted revision 37 from 1.3.2 tag back into trunk to avoid having a branch for this tag 5. created lightweight tags of all revisions that matched up with the contents of any tag in https://pytrainer.svn.sourceforge.net/svnroot/pytrainer/pytrainer/tags/ except 1.5.0.0.1 (preserving 1.5.0.0.1 was too difficult) 7. cloned git-svn repository in to clean git repository: $ git clone pytrainer-git-migration pytrainer-git 8. remove git-svn remote repository from new clone $ cd pytrainer-git $ git remote rm origin 9. moved the current 1.9.1 work on to a new branch and make master based on 1.9.0 tag: $ git branch -m master 1.9.x $ git checkout -b master v1.9.0 10. upload branches and tags to sourceforge: $ git remote add origin ssh://ncjo...@git.code.sf.net/u/ncjones/pytrainer $ git push origin master 1.9.x $ git push origin v1.9.0 v1.8.0 v1.7.2 (etc...) - Nathan On 16 November 2011 04:34, David García Granda <dgra...@gmail.com> wrote: > Hi, > > >>> While running these days I have been thinking about a better approach >>> to incorporate new functionalities to pytrainer to avoid submitting >>> all changes to trunk. Yes, I am talking about branches. >>> >>> What I have read and heard is that git has simpler ways to manage >>> branches and maybe after releasing 1.9.0 it is a good excuse to >>> migrate from svn to git. Any ideas or comments? >>> >>> Regards, >>> >>> David >>> >> >> I have been testing Subversion to Git migrations. This week I am going >> to try migrating the Pytrainer Subversion repository to Git. If it's >> successful I'll push it into a public repository. From there anyone >> will be able to clone it and have a play with it. If we're happy with >> it we can stop using Subversion. > > I did some tests in GitHub (https://github.com/dgranda/pytrainer/), > but I am not happy with the result. > > In addition, git support is enabled in SourceForge > (https://sourceforge.net/scm/?type=git&group_id=213157), but > repository not migrated yet. > > Regards, > > David > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Pytrainer-devel mailing list > Pytrainer-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pytrainer-devel > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
