From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: mark.kettenis@xs4all.nl, joseph@codesourcery.com,
kevinb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: Assume solib.h
Date: Tue, 16 Nov 2004 05:00:00 -0000 [thread overview]
Message-ID: <01c4cb98$Blat.v2.2.2$fc133040@zahav.net.il> (raw)
In-Reply-To: <419942CB.4000905@gnu.org> (message from Andrew Cagney on Mon, 15 Nov 2004 18:59:07 -0500)
> Date: Mon, 15 Nov 2004 18:59:07 -0500
> From: Andrew Cagney <cagney@gnu.org>
> Cc: mark.kettenis@xs4all.nl, joseph@codesourcery.com, kevinb@redhat.com,
> gdb-patches@sources.redhat.com
>
>
> > I'm with Mark on this one: a patch that potentially breaks a supported
> > platform doesn't get my vote. If a platform is supported, it deserves
> > that we don't break it, and calling it ``marginal'' doesn't change
> > anything.
>
> Eli, can you perhaphs explain what exactly you mean by "supported"
Like Daniel, I consider "supported" any target for which GDB builds
and works, and which is not declared deprecated.
> how the GNU project benefits by expending already limited resources
> on continually fixing vax-ultrix - a non GNU system
The same way it benefits by expending already limited resources on
fixing other targets--by being useful to our users.
> and how my change breaks it?
This part I don't know the details about. Mark said that it does
break, and I spoke on the assumption that you agree with the fact of
breakage, but don't consider it important.
next prev parent reply other threads:[~2004-11-16 5:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 19:39 Andrew Cagney
2004-11-11 20:06 ` Mark Kettenis
2004-11-11 21:48 ` Andrew Cagney
2004-11-11 22:24 ` Mark Kettenis
2004-11-12 15:52 ` Andrew Cagney
2004-11-12 17:20 ` Eli Zaretskii
2004-11-15 21:32 ` Kevin Buettner
2004-11-15 23:35 ` Mark Kettenis
2004-11-17 17:35 ` Eli Zaretskii
2004-11-15 23:59 ` Andrew Cagney
2004-11-16 1:20 ` Daniel Jacobowitz
2004-11-16 5:00 ` Eli Zaretskii [this message]
2004-11-16 8:37 ` Mark Kettenis
2004-11-16 20:54 ` Eli Zaretskii
2004-11-16 16:14 ` Andrew Cagney
2004-11-16 19:18 ` Mark Kettenis
2004-11-18 14:10 ` Andrew Cagney
2004-11-18 14:37 ` Mark Kettenis
2004-11-18 17:28 ` Kevin Buettner
2004-11-19 17:11 ` Andrew Cagney
2004-11-19 17:25 ` Randolph Chung
2004-11-19 17:36 ` Joel Brobecker
2004-11-19 17:40 ` Randolph Chung
2004-11-19 17:56 ` Joel Brobecker
2004-11-19 19:29 ` Joseph S. Myers
2004-11-16 21:06 ` Eli Zaretskii
2004-11-16 22:27 ` Andrew Cagney
2004-11-17 4:52 ` Eli Zaretskii
2004-11-16 1:40 ` Daniel Jacobowitz
2004-11-16 4:54 ` Eli Zaretskii
2004-11-16 16:31 ` Andrew Cagney
2004-11-16 19:45 ` Mark Kettenis
2004-11-16 21:06 ` Eli Zaretskii
2004-11-12 1:11 ` Randolph Chung
2004-11-13 1:10 ` 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='01c4cb98$Blat.v2.2.2$fc133040@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=joseph@codesourcery.com \
--cc=kevinb@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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