Hi Branden,
Yes, you can clone the latest and use "hg pull -u" to update to the latest. It's 230M because it includes every changeset ever, so it will only increase over time.
On Tue, Oct 5, 2010 at 11:19 AM, Branden Timm btimm@wisc.edu wrote:
Hello, I am trying to figure out the best way to use subversion to track both galaxy-central and our local tool integration work. We are standardized on subversion, so I'd like to use it if possible. What I've done so far:
Downloaded the latest galaxy-central 'hg clone https://bitbucket.org/galaxy/galaxy-central' Copied galaxy-central, including mercurial info, into the /trunk subdirectory of my repo.
My plan is that when future revisions to galaxy-central are available, I can create a new branch, use hg pull to update the codebase, test, and finally merge that branch back into /trunk.
I noticed that just the size of the galaxy-central mercurial repo is about 230M. Is this because back-versions are being included? If so, should I just do a clone to the most recent revision and then use 'hg pull' to apply future revisions?
Cheers
-- Branden Timm University of Wisconsin Great Lakes Bioenergy Research Center btimm@glbrc.wisc.edu _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev