Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: mark@codesourcery.com
Cc: neroden@doctormoo.dyndns.org, gcc-patches@gcc.gnu.org,
	gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: don't build send-pr,prms,gnats.tar
Date: Tue, 02 Jul 2002 14:36:00 -0000	[thread overview]
Message-ID: <200207022135.g62LZu020212@greed.delorie.com> (raw)
In-Reply-To: <57280000.1025640066@warlock.codesourcery.com> (message from Mark Mitchell on Tue, 02 Jul 2002 13:01:06 -0700)


> On the other hand, I think it's important we clarify this somewhat;
> I have already received one email asking a question about whether or
> not your message implies that Red Hat is somehow "special".  So, I
> am going to try to answer that question here.

Right, sorry, that was my "dj as a red hat employee" response, not my
"dj as a maintainer" response.  The pattern is this: we ask if
anyone's using a target, if either (1) nobody says they are, or (2)
someone knows why the target is there and can explain why it isn't
needed, then we take it out.  In this case, I knew RH was using it so
I spoke up.  If anyone else spoke up for their targets, we would have
kept those as well.  Usually, of course, Stan tells us the sordid
history of the target and we all agree to remove it ;)

Obviously, if there's a benefit to removing something RH still needs,
well, that's RH's problem.  If we (RH) can't justify it to the net
community, we (RH) will just have to figure out a way to deal with it.

Sorry for the confusion.


       reply	other threads:[~2002-07-02 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57280000.1025640066@warlock.codesourcery.com>
2002-07-02 14:36 ` DJ Delorie [this message]
2002-07-02 15:24   ` Mark Mitchell
2002-07-02 11:29 [patch] " Nathanael Nerode
2002-07-02 12:03 ` DJ Delorie

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=200207022135.g62LZu020212@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark@codesourcery.com \
    --cc=neroden@doctormoo.dyndns.org \
    /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