On 11/2/07, Karl Fogel <kfogel@red-bean.com> wrote:
> Note that this is how we're working in the Subversion repository right
> now. You make a branch, do your work there, and then push ("pull",
> whatever) the changes to trunk when they're ready. The developer who
> made the change could do that merge, or someone else could, it doesn't
> matter. The point is that this method works fine with Subversion.
> Commits are certainly not inherently "scary things".
The important thing about GIT and other DVCSs is that they make
merging {simple, trivial, elegant, pleasant} right from the start. We
can talk all we want about how we can emulate the same freedom in
Subversion or CVS by "just committing lots of half-baked changes to a
private branch"... but users are *averse* to that. Not because of a
"rigid policy mindset", but because merging back (or heaven forbid --
merging back and forth!) has always been so darn hard. DVCS removes
that barrier. And hopefully SVN 1.5 will do the same. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 2 14:35:57 2007