From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@elta.co.il
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: [commit] Deprecate remaining STREQ uses
Date: Sun, 14 Dec 2003 16:02:00 -0000 [thread overview]
Message-ID: <20031214160224.0FF864B412@berman.michael-chastain.com> (raw)
Hi Eli,
> However, running the script once a month (on the then-latest snapshot,
> I presume) is not something that I can afford, and I don't see anyone
> else stepping forward to do that for me.
If you can't commit 1-2 hours per month to test djgpp gdb, how are you
going to respond to bug reports and patches? What's going to happen
when it bit rots and stops building?
I think you should reconsider whether you have the resources to be a
maintainer for djgpp gdb.
> Since your proposal for deprecating counts minor releases, would it
> be enough to request a run for every such release?
In my opinion, no.
> Isn't it better to start deprecating only if we know that some code
> specific to a platform is broken by a certain change to GDB?
Again, in my opinion, no.
The official gdb definition of "supported" is "gdb builds and break main;
run" works. Personally, I think that's lame. However, what we have
right now is a situation where we aren't even working to that standard.
Michael C
next reply other threads:[~2003-12-14 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 16:02 Michael Elizabeth Chastain [this message]
2003-12-14 18:13 ` 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-15 6:22 Michael Elizabeth Chastain
2003-12-15 6:39 ` Eli Zaretskii
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
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=20031214160224.0FF864B412@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=eliz@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