From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: additions to GCC 3.2 build status list
Date: Sat, 23 Nov 2002 08:49:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.50.0211231013140.59038-100000@pulcherrima.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20021122164146.A2667@us.ibm.com>
On Fri, 22 Nov 2002, Janis Johnson wrote:
> otherwise I'll add the links and then occasionally send messages like
> this with a list of what new entries have been added, possibly copied to
> the people who posted the build reports.
I think it's a good idea to provide some feedback to those who cared
about reporting their results; a cumulative response seems fine, though.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2002-11-23 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 1:14 Janis Johnson
2002-11-23 1:27 ` kwall
2002-11-23 4:17 ` Kaveh R. Ghazi
2002-11-23 8:49 ` Gerald Pfeifer [this message]
2003-02-25 21:49 Janis Johnson
2003-02-26 3:39 ` Gabriel Dos Reis
2003-05-09 23:12 Janis Johnson
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=Pine.BSF.4.50.0211231013140.59038-100000@pulcherrima.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
/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).