Am Montag, 20. April 2009 10:59:34 schrieb Richard Guenther:
On Mon, 20 Apr 2009, Adrian Schröter wrote:
Just some background info for the list as TOFU:
You can already get the latest working ancestor via the API via lastworking=1 parameter. (something what the osc merge support will use). But it is true that this is not necessary the same version where the automatic created patch in source links has been created from.
So it might become an option in future to do the different merge order as Andreas has described. Practically it means the submitter has to adapt the changes made by other people to get his stuff working again. We will see if this works better or not.
It's not a question of "works better nor not" it is a question about correctness.
And this is very subjective. I personally feel much safer when I rebase my own old patch to the new version of the package, instead of being enforced to rethink other people changes. It is true that the old patch was intended to based on the old revision. But all mentioned use cases here where to adapt this submission to the new revision of the source package. You are of course right when you think about patches coming all from the same group of people. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org