On Tue, Apr 23, 2013 at 10:47:40AM +0200, Dirk Müller wrote:
2013/4/23 Marcus Meissner <meissner@suse.de>:
This is not about potential problems, this is about agreement to keep the .changes file linear.
Hi Marcus,
As soon as there is more than one code branch, it is not possible to keep the changes file linear. the _only_ way to do that would be to add all changes from all branches to the .changes file of all branches (which is tiresome), which means that I would get review declines from AJ then that says "your .changes say: add patch folsom-backport-XYZ.diff, but the patch is not in the package!"
Could you please explain me how you want to keep the rule of a changes file being only linear and having two code branches at the same time?
I answered this already, but again: Whats actually a part the review team should decide and offer for discussion, as so far the official stated policy apparently conflicts with the status quo. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org