On Sat, Sep 8, 2012 at 6:41 AM, <mar...@v.loewis.de> wrote: > > Zitat von Stefan Krah <ste...@bytereef.org>: > > After all, 99.99% of issues are either found by developers themselves or >> by gcc, Visual Studio, Valgrind, etc. It just occurred to me that for >> example >> we don't credit other tools in commit messages. >> > > I agree that Coverity doesn't need to be mentioned in commit message. > We do cite tools occasionally, but in a negative way, such as "silence > gcc warning", where the commit message and/or comment explains why some > code is ugly for some non-obvious reason. >
Well, when I fix bugs found by Clang's static analyzer (which I ran out time to do for 3.3) I try to remember to thank the tool. IOW I don't think thanking a tool hurts, but in no way is required required either.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
