Hi,
I just wanted to let you know that I recently did a git-svn download of the subversion repo. It took quite some time, so to save others time I thought I'd make it available.
I _don't_ recommend using this for working on svn branches, since it imported the branches a bit strangely due to the somewhat non-standard way the /branches folder is organized. However, if you're working off of the trunk it's fine. Also, you can easily make local branches off of the trunk, work work work, and then at some point when you want to commit, you download the latest trunk with:
git-svn rebase
Then manually rebase the local branch you've been working on,
git-checkout <mybranch> git-rebase master
Then dump in your new commits:
git-svn dcommit
More likely this is useful for generating patches against the main trunk to be submitted to the patch tracker:
git-diff master..<mybranch>
(That way even people without svn access can version-control their proposed patches before they are even accepted and applied.)
If you're not at all interested in using git, ignore this message.. I don't think git-svn is a good starting point for learning git, but if you're used to it and like it, this might be useful to you.
You can download my tarball of the repo here: http://www.music.mcgill.ca/~sinclair/pub/puredata-gitsvn-150208.tar.bz2
Untar it and then do "git-svn rebase" to grab the latest changes. (I give a tarball instead of suggesting git-clone because git-clone doesn't copy important svn-related stuff.)
Some interesting info.. After downloading the whole svn history, the .git folder was something like 540 MB. After "git-gc --aggressive", which repacks and compresses the history database, it was about 74 MB. Not bad.. :) That's for the whole history of pure-data.
Steve
This would be good to have on the site, something like
http://puredata.info/docs/developer/git-svn
.hc
On Feb 19, 2008, at 4:45 PM, Stephen Sinclair wrote:
Hi,
I just wanted to let you know that I recently did a git-svn download of the subversion repo. It took quite some time, so to save others time I thought I'd make it available.
I _don't_ recommend using this for working on svn branches, since it imported the branches a bit strangely due to the somewhat non-standard way the /branches folder is organized. However, if you're working off of the trunk it's fine. Also, you can easily make local branches off of the trunk, work work work, and then at some point when you want to commit, you download the latest trunk with:
git-svn rebase
Then manually rebase the local branch you've been working on,
git-checkout <mybranch> git-rebase master
Then dump in your new commits:
git-svn dcommit
More likely this is useful for generating patches against the main trunk to be submitted to the patch tracker:
git-diff master..<mybranch>
(That way even people without svn access can version-control their proposed patches before they are even accepted and applied.)
If you're not at all interested in using git, ignore this message.. I don't think git-svn is a good starting point for learning git, but if you're used to it and like it, this might be useful to you.
You can download my tarball of the repo here: http://www.music.mcgill.ca/~sinclair/pub/puredata- gitsvn-150208.tar.bz2
Untar it and then do "git-svn rebase" to grab the latest changes. (I give a tarball instead of suggesting git-clone because git-clone doesn't copy important svn-related stuff.)
Some interesting info.. After downloading the whole svn history, the .git folder was something like 540 MB. After "git-gc --aggressive", which repacks and compresses the history database, it was about 74 MB. Not bad.. :) That's for the whole history of pure-data.
Steve
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
News is what people want to keep hidden and everything else is publicity. - Bill Moyers
-
Hans-Christoph Steiner -
Stephen Sinclair