From: DJ Delorie <dj@redhat.com>
To: neroden@doctormoo.dyndns.org
Cc: 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 12:03:00 -0000 [thread overview]
Message-ID: <200207021902.g62J2Uc18022@greed.delorie.com> (raw)
In-Reply-To: <20020702182717.GA18022@doctormoo.dyndns.org> (message from Nathanael Nerode on Tue, 2 Jul 2002 14:27:17 -0400)
> 2002-07-02 Nathanael Nerode <neroden@gcc.gnu.org>
>
> * Makefile.in: Don't build prms, send-pr, or GNATS tar files.
> * configure.in: Ditto.
Red Hat still uses send-pr internally. I don't think we use prms
internally though, but safer to just leave those in place for now
since they're all related.
next prev parent reply other threads:[~2002-07-02 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 11:29 [patch] " Nathanael Nerode
2002-07-02 12:03 ` DJ Delorie [this message]
2002-07-02 13:02 ` Mark Mitchell
2002-07-02 14:36 ` DJ Delorie
2002-07-02 15:24 ` Mark Mitchell
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=200207021902.g62J2Uc18022@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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).