From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: msnyder@sonic.net
Cc: nickrob@snap.net.nz, msnyder@sonic.net, gdb-patches@sourceware.org
Subject: Re: NEWS for 6.7: mention coverity bug fixes
Date: Mon, 20 Aug 2007 19:11:00 -0000 [thread overview]
Message-ID: <200708201911.l7KJBF0D023666@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <16498.12.7.175.2.1187635019.squirrel@webmail.sonic.net> (msnyder@sonic.net)
> Date: Mon, 20 Aug 2007 11:36:59 -0700 (PDT)
> From: msnyder@sonic.net
>
> There is precident for acknowledging the contributions of
> institutions and corporations in the NEWS file:
>
> Configurations for embedded MIPS now include a simulator
> contributed by Cygnus Solutions.
>
> Sparc configurations may now include the ERC32 simulator
> contributed by the European Space Agency.
>
> What's wrong with acknowledging what Coverity has contributed?
I don't think there anything wrong with that, unless we know Coverity
is actively working against the Free Software communitiy.
I do think however that your origional phrasing was a bit odd.
"Coverity Issues" isn't really a meaningful description. I'd prefer
if you added some sort of description about the class of bugs fixed
and then add a variation on what you show above, like "found by
Coverity Inc.".
Mark
prev parent reply other threads:[~2007-08-20 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 19:12 msnyder
2007-08-17 20:31 ` Eli Zaretskii
2007-08-17 21:03 ` msnyder
2007-08-18 6:46 ` Eli Zaretskii
2007-08-18 1:05 ` Nick Roberts
2007-08-18 5:08 ` Michael Snyder
2007-08-18 8:52 ` Nick Roberts
2007-08-18 15:39 ` Michael Snyder
2007-08-20 10:42 ` Nick Roberts
2007-08-20 11:29 ` Daniel Jacobowitz
2007-08-20 18:37 ` msnyder
2007-08-20 18:42 ` msnyder
2007-08-21 6:47 ` Nick Roberts
2007-08-20 19:11 ` Mark Kettenis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200708201911.l7KJBF0D023666@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox