Cherrypick without merge needed
JetMark
extrapic at extrapic.com
Wed Jul 2 18:56:20 BST 2008
I understand that you, and its clear others do not think that replaying the
state of the file system or "fast-forwarding" is a good way to do things and
I am not offended.
I am absolutely certain that you and others have missed something here. By
being choosy about which changes are picked and which combination, in such a
way that the only versions of files presented to the build are those exact
versions that have been eyeballed by the developers already is a massive
win. I am not saying do this all that time, but just that knowing the status
really does mean that a second eyeballing is not needed. Bazaar and other
SCM's should do this. Maybe GIT does. I am suggesting adding something extra
so that I as a CM can know.
Would have written the code too. Sad thing is that my choice of Bazaar (in
spite of these worries) has been overidden by people who actually know even
less than you think I do. So we will likely use subversion.
But the fact remains that this is a feature that ought to be added to Bazaar
and added in such a way as to add without causing people to behave in a CVS
like manner!
--
View this message in context: http://www.nabble.com/Cherrypick-without-merge-needed-tp18212682p18243269.html
Sent from the Bazaar - General Discussion mailing list archive at Nabble.com.
More information about the bazaar
mailing list