Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: David Carlton <carlton@kealia.com>
Cc: mec.gnu@mindspring.com,gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <uoequ7kst.fsf@elta.co.il> (raw)
In-Reply-To: <yf2vfl3xniv.fsf@hawaii.kealia.com> (message from David Carlton on Wed, 17 Mar 2004 11:48:56 -0800)

> From: David Carlton <carlton@kealia.com>
> Date: Wed, 17 Mar 2004 11:48:56 -0800
> 
> I think one of the things that is bothering me is that we're
> highlighting new bugs but not highlighting bugs that have been fixed.

Fixed bugs that we want to tell users about should be in NEWS.

> Some of the latter is in NEWS, but NEWS is both at a higher level (it
> doesn't mention specific PR numbers) and it tends to concentrate on
> new features, which isn't quite the same thing.

There's nothing to prevent us from adding fixed bugs to NEWS, I think.

However, if the number of bugs fixed between releases is very large,
it could make sense not to mention them at all.  One case in point is
Emacs: its NEWS contains only new and improved features, while the
fixed bugs are not mentioned at all, their number being too huge.

> For GCC releases,
> Gerald Pfeifer (if I'm remembering correctly) goes through the list of
> GCC bugs and provides a table of all of the ones that have been fixed
> in that particular release (breaking them down into categories);
> besides making GCC developers feel good, it can also help users decide
> when to upgrade, because they can look at the list of bugs that have
> been fixed in the categories that they care about and see how
> important those bugs are to them.

I sincerely doubt that the list of GCC fixed bugs helps anyone beyond
GCC developers and people with special interest in compiler
development, as most of them are worded in a way that leaves users
with a ``Huh?'' after-taste.


WARNING: multiple messages have this Message-ID
From: Eli Zaretskii <eliz@elta.co.il>
To: David Carlton <carlton@kealia.com>
Cc: mec.gnu@mindspring.com,gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Thu, 18 Mar 2004 06:06:00 -0000	[thread overview]
Message-ID: <uoequ7kst.fsf@elta.co.il> (raw)
Message-ID: <20040318060600.nxWR0s5jD1MYuvzraFTw2mFggbBW9OSPF6GDkGDt8jA@z> (raw)
In-Reply-To: <yf2vfl3xniv.fsf@hawaii.kealia.com> (message from David Carlton on Wed, 17 Mar 2004 11:48:56 -0800)

> From: David Carlton <carlton@kealia.com>
> Date: Wed, 17 Mar 2004 11:48:56 -0800
> 
> I think one of the things that is bothering me is that we're
> highlighting new bugs but not highlighting bugs that have been fixed.

Fixed bugs that we want to tell users about should be in NEWS.

> Some of the latter is in NEWS, but NEWS is both at a higher level (it
> doesn't mention specific PR numbers) and it tends to concentrate on
> new features, which isn't quite the same thing.

There's nothing to prevent us from adding fixed bugs to NEWS, I think.

However, if the number of bugs fixed between releases is very large,
it could make sense not to mention them at all.  One case in point is
Emacs: its NEWS contains only new and improved features, while the
fixed bugs are not mentioned at all, their number being too huge.

> For GCC releases,
> Gerald Pfeifer (if I'm remembering correctly) goes through the list of
> GCC bugs and provides a table of all of the ones that have been fixed
> in that particular release (breaking them down into categories);
> besides making GCC developers feel good, it can also help users decide
> when to upgrade, because they can look at the list of bugs that have
> been fixed in the categories that they care about and see how
> important those bugs are to them.

I sincerely doubt that the list of GCC fixed bugs helps anyone beyond
GCC developers and people with special interest in compiler
development, as most of them are worded in a way that leaves users
with a ``Huh?'' after-taste.


  reply	other threads:[~2004-03-18  6:06 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 19:30 ` Michael Elizabeth Chastain
2004-03-17 19:48 ` David Carlton
2004-03-19  0:09   ` Eli Zaretskii [this message]
2004-03-18  6:06     ` Eli Zaretskii
2004-03-19  0:09   ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17  6:58 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-18 16:23 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` David Carlton
2004-03-18 16:45   ` David Carlton
2004-03-19  0:09 ` Andrew Cagney
2004-03-19  0:27   ` Daniel Jacobowitz
2004-03-19 14:56     ` Eli Zaretskii
2004-03-19 15:03     ` Andrew Cagney
2004-03-19 15:33       ` Eli Zaretskii
2004-03-19 15:54         ` Andrew Cagney
2004-03-20 15:38           ` Eli Zaretskii
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 20:15 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 18:21 ` Michael Elizabeth Chastain
2004-03-17 22:11 ` Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 19:21 ` Michael Elizabeth Chastain
2004-03-17 22:54 Michael Elizabeth Chastain
2004-03-17 23:39 ` Andrew Cagney
2004-03-18  6:16   ` Eli Zaretskii
2004-03-18 16:05     ` Andrew Cagney
2004-03-18 16:52       ` Eli Zaretskii
2004-03-19  0:09         ` Eli Zaretskii
2004-03-19  0:09       ` Andrew Cagney
2004-03-19  0:09     ` Eli Zaretskii
2004-03-19  0:09   ` Andrew Cagney
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-17 18:55 Michael Elizabeth Chastain
2004-03-17 19:03 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09 ` David Carlton
2004-03-17 19:16   ` David Carlton
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-17  1:53 Michael Elizabeth Chastain
2004-03-17 16:13 ` Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney
2004-03-17 17:05 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09 ` Eli Zaretskii
2004-03-17  6:16   ` Eli Zaretskii
2004-03-19  0:09 ` David Carlton
2004-03-17 17:19   ` David Carlton
2004-03-19  0:09   ` Eli Zaretskii
2004-03-17 19:07     ` Eli Zaretskii
2004-03-19  0:09     ` David Carlton
2004-03-17 19:18       ` David Carlton
2004-03-19  0:09     ` Andrew Cagney
2004-03-17 22:11       ` Andrew Cagney
2004-03-19  0:09       ` Eli Zaretskii
2004-03-18  6:11         ` Eli Zaretskii
2004-03-18 16:36         ` Daniel Jacobowitz
2004-03-19  0:09           ` Eli Zaretskii
2004-03-18 16:55             ` Eli Zaretskii
2004-03-19  0:09           ` Daniel Jacobowitz
2004-03-19  0:09           ` Andrew Cagney
2004-03-19  0:25             ` Daniel Jacobowitz
2004-03-19  0:09 ` Michael Elizabeth Chastain

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=uoequ7kst.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /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