Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-September/121624.html below:

[Python-Dev] Coverity scan

• Previous message: [Python-Dev] Coverity scan
• Next message: [Python-Dev] Coverity scan
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Zitat von Stefan Krah <stefan at 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.

Regards,
Martin

• Previous message: [Python-Dev] Coverity scan
• Next message: [Python-Dev] Coverity scan
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4