> The problem now is that patches in the development branch are > "forgotten" and not backported when appropiate
Sorry, do you have real examples of this? > If we up-port, no patch is forgotten. The rule should be: "patches in > n+1 are a SUPERSET of patches in n". With this rule, mercurial takes > care of everything (a patch in n+1 can 'undo' a patch up-ported from n, > if needed, keeping the rule). That's a theoretical and IMO naïve point of view. In practice, there are many changesets that will not "up-port" cleanly and will need manual work. The work will not be much less than with down-porting. Regards Antoine. _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
