From: "Frank Ch. Eigler" <fche@redhat.com>
To: overseers@sourceware.org
Subject: Re: [Laurent GUERBY <laurent@guerby.net>] [SUMMARY] Old machine cluster for GCC compile/testing
Date: Fri, 12 Aug 2005 18:24:00 -0000 [thread overview]
Message-ID: <20050812182441.GA12253@redhat.com> (raw)
In-Reply-To: <m3ll37ggz2.fsf@gossamer.airs.com>
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
Hi -
> It's not clear to me who is going to administer these machines.
One option is that we sourceware/gcc.gnu.org overseers do *not* take
any administrative role over them. The GCC SC or gcc maintainers can
sort that out amongst themselves.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-08-12 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 18:14 Ian Lance Taylor
2005-08-12 18:24 ` Frank Ch. Eigler [this message]
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=20050812182441.GA12253@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sourceware.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).