From: "Eli Zaretskii" <eliz@elta.co.il>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add meaningful section titles to PROBLEMS
Date: Sat, 20 Mar 2004 15:26:00 -0000 [thread overview]
Message-ID: <1438-Sat20Mar2004172324+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040319174517.856F74B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Fri, 19 Mar 2004 12:45:17 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> When I upgrade a software package, I find the list of regressions from
> my current version to be of *great* value. For each new problem, I have
> to ascertain whether it affects my system. If it affects my system, I
> have to figure out how to work around the problem. If the problems are
> too severe, then I know that I am better off not upgrading.
I don't think regressions since version X.Y is something we need to
mention in PROBLEMS. It is an implicit assumption of users that when
they upgrade to a higher version, they have _less_ bugs, not more. If
some unfortunate release violates this principle to a high degree, we
should immediately make a bugfix release.
So I think known user-level bugs need to be mentioned, but it's not
very important to say in which release they appeared first.
next prev parent reply other threads:[~2004-03-20 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 17:45 Michael Elizabeth Chastain
2004-03-20 15:26 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 16:50 Michael Elizabeth Chastain
2004-03-19 17:22 ` Andrew Cagney
2004-03-19 16:16 Andrew Cagney
2004-03-19 17:13 ` David Carlton
2004-03-19 17:33 ` Andrew Cagney
2004-03-19 17:43 ` David Carlton
2004-03-19 19:59 ` Andrew Cagney
2004-03-20 15:22 ` Eli Zaretskii
2004-03-20 15:29 ` Eli Zaretskii
2004-03-20 15:34 ` Eli Zaretskii
2004-03-25 21:07 ` Andrew Cagney
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=1438-Sat20Mar2004172324+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--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