Victor Mote wrote:

 Branches imply
eventual merging,
Not necessarily.

I'll be happy to consider this point if someone will name even one benefit
to keeping code that will never be merged in the same tree.
Well, the main idea of branches is just to split development, e.g. for the sake of some release bug handling, but branches are not obliged to be merged eventually. Usual development pattern is to branch a release code and continue development with no care about it (bugs are fixed in the branch) and when a new release is ready all patches and bug fixes in branched code *may be* just irrelevant because of new (e.g. redesigned :) implemention.
Following this pattern, development of branched code is just ugly mess as it's first of all *maintenance* release.

Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to