On Fri, 2019-10-04 at 11:41 +0200, Stefan Seyfried wrote:
Are you really asking this question? Of course, sometimes I work on stuff with 10 years of changes and I do this regularly.
Then you will be delighted that you can use "git log" / "git blame" in the future instead of grepping bluez.changes.
Grepping "git log" will only be useful if we make it absolutely mandatory for the log messages to include the patch filenames being removed. Which I'm sure you'll whine about just as much as doing so in the .changes file, given it's exactly the same amount of work for exactly the same reasons. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg HRB 247165, AG München GF: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org