Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Michael Snyder" <msnyder@sonic.net>
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: <gdb-patches@sourceware.org>
Subject: Re: NEWS for 6.7: mention coverity bug fixes
Date: Sat, 18 Aug 2007 15:39:00 -0000	[thread overview]
Message-ID: <000501c7e1ad$9f415800$677ba8c0@sonic.net> (raw)
In-Reply-To: <18118.45892.919518.866568@kahikatea.snap.net.nz>


----- Original Message ----- 
From: "Nick Roberts" <nickrob@snap.net.nz>
To: "Michael Snyder" <msnyder@sonic.net>
Cc: <gdb-patches@sourceware.org>
Sent: Saturday, August 18, 2007 1:52 AM
Subject: Re: NEWS for 6.7: mention coverity bug fixes


> > > I can imagine that Coverity would like recognition when their software
is
>  > > successfully used to find bugs in free software projects, but I don't
>  > > think that NEWS is the right place to do it.  This file details what
>  > > changes have been made to GDB, not how they were made or how many
were
>  > > made.  You already mention Coverity in the ChangeLogs, which seems
the
>  > > right thing to do.  _They_ can then use this as evidence to any
claims
>  > > that they might wish to make about their software.
>  >
>  > Actually I stopped mentioning them in the changelogs, when
>  > one of the Binutils maintainers said that they thought it was
>  > inappropriate.
>
> I think I can see this in the archives where he suggests writing what he
calls
> a NEWS entry but then refers to http://gcc.gnu.org/news.html, for which
there
> appears to be no GDB equivalent.  I thought the NEWS _file_ was aimed at
the
> users of GDB.  To that extent the bug fixes made through Coverity are only
> relevant here if they provide a noticeable difference, e.g., users were
> complaining about crashes and leakages which have been fixed.
>
> I guess if Coverity is proprietary software then the Free Software line
may be
> that it gets no mention. However, the ChangeLog seems appropriate to me,
just
> as it is the place where the author gets recognition for his/her
contribution.

That was indeed my first thought.

Would you suggest, then, that I go back and annotate the 60 or so
change log entries I've made that refer to fixing Coverity issues?



  reply	other threads:[~2007-08-18 15:39 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 [this message]
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

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='000501c7e1ad$9f415800$677ba8c0@sonic.net' \
    --to=msnyder@sonic.net \
    --cc=gdb-patches@sourceware.org \
    --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