Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@gnu.org,gdb@sources.redhat.com
Subject: Re: [commit] Deprecate remaining STREQ uses
Date: Mon, 15 Dec 2003 06:39:00 -0000	[thread overview]
Message-ID: <ufzfmy452.fsf@elta.co.il> (raw)
In-Reply-To: <20031215062230.CD6E94B412@berman.michael-chastain.com> (mec.gnu@mindspring.com)

> Date: Mon, 15 Dec 2003 01:22:30 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> 
> eli> Since your proposal for deprecating counts minor releases, would it
> eli> be enough to request a run for every such release?
> mec> In my opinion, no.
> eli> Why not?
> 
> Known regressions still go months before fixing.  And I don't mean
> "months until the elusive bug can be duplicate"; I mean "months after I
> file a PR with a simple test case and a pointer to the exact patch where
> gdb broke".
> 
> Then consider how much worse this would be if I did one run per release
> instead of several runs per week.

I agree that your suggestion will probably leave us with less bugs.
But I'm concerned that we could inadvertently spill the baby, if we
assume that any port that hasn't seen official testing does not work
and should be obsoleted.

> eli> Isn't it better to start deprecating only if we know that some code
> eli> specific to a platform is broken by a certain change to GDB?
> mec> Again, in my opinion, no.
> eli> Again, why not?
> 
> Because nobody knows what change is going to break what platform.

I think quite a few changes are known to break platforms for which a
replacement for a deprecated interface was not submitted.

> And I'm getting tired of this conversation because I don't see any
> constructive action coming out of it.

I'm sorry I took your time; I thought this issue was important enough
to be discussed at some length.

The constructive action that could come out of this, in my view, is if
we agree that hasty removal of support for platforms is potentially
destructive and should be used with great caution.

What about others: am I the only one who thinks we shouldn't be
obsoleting platforms hastily for lack of officially-certified testing?

> I'm going to continue my
> aggressive QA campaign.  When I bump into someone, such as I've bumped
> into David Anglin or you, my attitude is going to be "well, what can you
> contribute to support the platform?"

My comment to this is that we should sometimes think about users, not
only developers.  Being overly harsh to the users by removing support
for their platforms too quickly is something I think we should avoid.


  reply	other threads:[~2003-12-15  6:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15  6:22 Michael Elizabeth Chastain
2003-12-15  6:39 ` Eli Zaretskii [this message]
2003-12-15 15:51   ` Daniel Jacobowitz
2003-12-16  6:30     ` Eli Zaretskii
2003-12-31 19:48       ` Andrew Cagney
2004-01-01  5:59         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2003-12-31 19:56 Michael Elizabeth Chastain
2004-01-01  6:03 ` Eli Zaretskii
2003-12-15 17:01 Michael Elizabeth Chastain
2003-12-14 16:02 Michael Elizabeth Chastain
2003-12-14 18:13 ` Eli Zaretskii
2003-12-14  8:25 Michael Elizabeth Chastain
2003-12-14 11:45 ` Eli Zaretskii
2003-12-14 14:44   ` Andrew Cagney
     [not found] <20031214062335.964804B412@berman.michael-chastain.com>
2003-12-14  6:34 ` Eli Zaretskii
     [not found] <3FC119EB.1060102@gnu.org>
     [not found] ` <ufzgee29u.fsf@elta.co.il>
     [not found]   ` <3FC234C0.1000500@gnu.org>
     [not found]     ` <20031124165047.GA2227@nevyn.them.org>
     [not found]       ` <1031124182547.ZM9776@localhost.localdomain>
     [not found]         ` <3FC26407.9000704@gnu.org>
     [not found]           ` <1031125000932.ZM11256@localhost.localdomain>
     [not found]             ` <3FC60A75.8090803@gnu.org>
     [not found]               ` <1031204044404.ZM3660@localhost.localdomain>
     [not found]                 ` <9743-Thu04Dec2003174358+0200-eliz@elta.co.il>
     [not found]                   ` <3FCF6FCA.30607@gnu.org>
     [not found]                     ` <1031212192642.ZM21819@localhost.localdomain>
     [not found]                       ` <3FDA64D0.7020306@gnu.org>
2003-12-13 20:03                         ` Jim Blandy
2003-12-14 16:24                           ` Andrew Cagney
2003-12-13 15:23 Michael Elizabeth Chastain
2003-12-13 16:31 ` Eli Zaretskii
2003-12-13 19:40   ` 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=ufzfmy452.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=cagney@gnu.org \
    --cc=gdb@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