From: "H . J . Lu" <hjl@lucon.org>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Michael Veksler <VEKSLER@il.ibm.com>,
Andrew Cagney <ac131313@cygnus.com>,
gdb@sources.redhat.com
Subject: Re: gdb 5.2 removes the conditional breakpoints
Date: Thu, 18 Apr 2002 09:42:00 -0000 [thread overview]
Message-ID: <20020418094202.C20868@lucon.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020418140052.5861A-100000@is>; from eliz@is.elta.co.il on Thu, Apr 18, 2002 at 02:08:41PM +0300
On Thu, Apr 18, 2002 at 02:08:41PM +0300, Eli Zaretskii wrote:
>
> Bugs which have relatively safe fixes will be fixed on the branch. Bugs
> that don't have safe fixes will have to wait for the next release. New
> features (as opposed to bugfixes) will have to wait, period.
>
> Please be aware of the downside of fixing everything indiscriminately: it
> means that GDB 5.2 will never be released, since ``there's always one
> more bug''. So what will go into the branch and what won't is a
> judgement call, not something that is self-evident.
>
That is a regression and a very bad one we are talking about. I believe
it is perfectly fine to delay a release to fix regressions. Otherwise,
people may find the new gdb less useful than the old ones or people
may say the new gdb is worse than the old ones.
BTW, I agree we shouldn't fix old bugs nor add new features on branch.
H.J.
next prev parent reply other threads:[~2002-04-18 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 23:40 Michael Veksler
2002-04-18 3:11 ` Eli Zaretskii
2002-04-18 9:31 ` H . J . Lu
2002-04-18 10:22 ` Daniel Jacobowitz
2002-04-18 10:34 ` H . J . Lu
2002-04-18 10:41 ` Daniel Jacobowitz
2002-04-18 9:42 ` H . J . Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 0:52 Michael Veksler
2002-04-17 16:57 ` H . J . Lu
2002-04-17 17:34 ` Andrew Cagney
2002-04-17 17:48 ` H . J . Lu
2002-04-17 20:20 ` Andrew Cagney
2002-03-22 9:50 H . J . Lu
2002-03-22 10:24 ` Andrew Cagney
2002-03-22 10:45 ` H . J . Lu
2002-03-22 10:27 ` Daniel Jacobowitz
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=20020418094202.C20868@lucon.org \
--to=hjl@lucon.org \
--cc=VEKSLER@il.ibm.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.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