A friendly reminder that per the MDN commit rules, the use of "No bug" in the commit message is to be used sparingly - in general for minor things like whitespace changes/comment fixes/etc where traceability isn't as important. https://developer.mozilla.org/docs/Mozilla/Developer_guide/Committing_Rules_and_Responsibilities
I've come across uses of "No bug" commits recently where entire upstream imports of vendored libraries were done. This is bad for multiple reasons: * If makes sheriffing difficult - if the patch is broken and needs backing out, where should the comment go? When it gets merged to mozilla-central, who gets notified? * It makes tracking a pain - what happens if that patch ends up needing uplift? What about when that patch causes conflicts with another patch needing uplift? What if it causes a regression and a blocking bug needs to be filed? Bugs are cheap. Please use them. Thanks, Ryan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
