From: Jeffrey A Law <law@redhat.com>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: overseers@gcc.gnu.org
Subject: Re: gcc-help@gcc.gnu.org: mailing list or help address for gcc@?
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <11222.977120331@upchuck> (raw)
In-Reply-To: <orlmtentpz.fsf@guarana.lsd.ic.unicamp.br>
In message < orlmtentpz.fsf@guarana.lsd.ic.unicamp.br >you write:
> On Dec 17, 2000, Jeffrey A Law <law@redhat.com> wrote:
>
> > Unfortunately, RMS decreed that we must continue to support gcc-help
> > back when the EGCS & GCC projects merged.
>
> Would renaming the list to, say, gcc-install, be too painful?
Yes.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@redhat.com>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: overseers@gcc.gnu.org
Subject: Re: gcc-help@gcc.gnu.org: mailing list or help address for gcc@?
Date: Sun, 17 Dec 2000 22:16:00 -0000 [thread overview]
Message-ID: <11222.977120331@upchuck> (raw)
Message-ID: <20001217221600.fsOgKPHfDqFp6ZsykUM9gnyCejaz-2JV9PqBBtGNIhk@z> (raw)
In-Reply-To: <orlmtentpz.fsf@guarana.lsd.ic.unicamp.br>
In message < orlmtentpz.fsf@guarana.lsd.ic.unicamp.br >you write:
> On Dec 17, 2000, Jeffrey A Law <law@redhat.com> wrote:
>
> > Unfortunately, RMS decreed that we must continue to support gcc-help
> > back when the EGCS & GCC projects merged.
>
> Would renaming the list to, say, gcc-install, be too painful?
Yes.
jeff
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Alexandre Oliva
2000-12-17 19:49 ` Alexandre Oliva
2000-12-30 6:08 ` Jeffrey A Law
2000-12-17 22:00 ` Jeffrey A Law
2000-12-30 6:08 ` Alexandre Oliva
2000-12-17 22:12 ` Alexandre Oliva
2000-12-30 6:08 ` Jeffrey A Law [this message]
2000-12-17 22:16 ` Jeffrey A Law
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=11222.977120331@upchuck \
--to=law@redhat.com \
--cc=oliva@lsd.ic.unicamp.br \
--cc=overseers@gcc.gnu.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).