I have re-synchronised my Pytrainer git repository with the Pytrainer subversion repository (see https://sourceforge.net/u/ncjones/pytrainer). This is how I did it:
1. clone the svn trunk into a new git repository from the revision you want to update from: $ git svn clone -A users.txt --no-metadata -r938:HEAD https://pytrainer.svn.sourceforge.net/svnroot/pytrainer/pytrainer/trunk pytrainer-trunk 2. add the git svn repository as a remote to the real git repository and fetch it's contents: $ cd ../pytrainer-git $ git remote add svn-trunk file:///home/nathan/dev/code/pytrainer-trunk $ git fetch svn-trunk 3. cherry pick all changes onto the master branch 5. push the master branch to sourceforge $ git push origin master - Nathan ------------------------------------------------------------------------------ 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
