From: Alexandre Oliva <aoliva@redhat.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc-patches@gcc.gnu.org, <gcc@gcc.gnu.org>,
Mark Mitchell <mark@codesourcery.com>
Subject: Re: Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4)
Date: Fri, 26 Apr 2002 08:56:00 -0000 [thread overview]
Message-ID: <org01ia26l.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at>
On Apr 26, 2002, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:
> This is an issue that has been coming up quite often, recently, and
> even in the context of regular contributors like you, so apparently
> there is a communications problem.
I supposed the problem was on my end, just because I was 2-3 weeks
behind in the GCC mailing lists. It didn't occur to me to look for
the information in the web site, anyway :-(
Thanks,
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-04-26 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <oradrt6uzy.fsf@free.redhat.lsd.ic.unicamp.br>
2002-04-26 4:20 ` Gerald Pfeifer
2002-04-26 8:56 ` Alexandre Oliva [this message]
2002-04-26 10:48 ` Mark Mitchell
[not found] ` <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at>
2002-04-26 13:04 ` Current GCC status (was: PATCH: Fix in-source configuration regressionfrom " Jonathan Lennox
2002-04-26 14:06 ` Gerald Pfeifer
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=org01ia26l.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).