On Tue, 4 Mar 2008, Ralf Wildenhues wrote:
As far as cramping Gary's style goes, Gary (only used as an example
here) is prone to making large changes, and these changes may soon
render 'master' useless as a good source of patches for stable branches.
Ah, no, this problem is easily avoided. git cherry-pick allows you to
pick individual patches from one branch into another.
My point is that as the master version advances in time, the baseline
for submitted patches will become more and more different.
Eventually a patch from the master version can not reasonably be
applied against a stable branch.
One reason why I have not contributed all that much to libtool sources
is that the level of effort to produce an emailable patch for peer
approval on this list substantially "raises the bar" for contribution.
While the patch is waiting to be approved, the local changes sit
uncommitted in a working directory, hindering further work on the same
files. Each developer needed to develop his own system for working
around this limitation. I never did. It seems that git has much more
to offer to meet these needs than CVS does.
Bob
======================================
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
