RE: merge performance (was: Re: Distributed Subversion)
From: Trent Nelson <tnelson_at_onresolve.com>
Date: Thu, 11 Jun 2009 22:00:25 +0100
> Subversion's merge tracking allows you to merge from only a subset
I'm interested to hear how much use this 'feature' gets in the wild.
Anyone out there in the user base fanatical about this feature? Is anyone relying on it heavily? Has the introduction of this feature in 1.5 allowed you to finally drop the 'burden' of 1.4+svnmerge.py?
Personally, as much as I hate to admit it, the more I work with 1.5+, the more I wish I could go back to the 1.4 days with svnmerge.py. I'm quite surprised how obtuse `svn merge` is in comparison to svnmerge.py:
branches/foo>svnmerge.py avail
trunk>svnmerge.py merge foo
branches/foo>svnmerge.py block 100
Am I alone?
For what it's worth, my Subversion utopia looks something like this:
trunk>svn branch foo
branches/foo>svn sync
branches/foo>svn sync
branches/foo>svn status
branches/foo>svn deliver
branches/foo>svn retire
tags>ls
trunk>tag 2009.06
tags/2009.06.3>echo foo > foo.txt && svn add foo.txt && svn ci -m ""
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.