>>> The "Fixes" tag is an indication that the patch should be backported. >> >> No it's not that strong. It's an indication that the patch fixes another >> commit, which may or may not mean it should be backported depending on >> the preferences of the backporter. If it *does* need backporting then >> the Fixes tag helps identify where it should go. > > Thank you for setting the record straight. > >> The doco is actually pretty well worded IMO: It seems that there are still interpretations left over for further clarification. Would any porters dare to distribute the deletion of questionable condition checks (and special error messages) to more software versions? >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n183 >> >> If your patch fixes a bug in a specific commit, e.g. you found an issue using >> ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of >> the SHA-1 ID, and the one line summary. Would you dare to categorise any software inefficiencies with a bug type? Regards, Markus
