public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: <Peter.Bienstman@rug.ac.be>
Cc: "Mark Mitchell" <mark@codesourcery.com>, <overseers@gcc.gnu.org>
Subject: Re: GCC 3.0 Bugs: Call for Volunteers
Date: Fri, 16 Feb 2001 13:19:00 -0000	[thread overview]
Message-ID: <87y9v65ncc.fsf@creche.redhat.com> (raw)
Message-ID: <20010216131900.xBoJ0EMJ107H-NuChgJgMUVNcuQQhUYF4OHrr_h_CuY@z> (raw)
In-Reply-To: <000001c095a3$9edaef50$0454c19d@intec.rug.ac.be>

>>>>> "Peter" == Peter Bienstman <Peter.Bienstman@rug.ac.be> writes:

Peter> I'd like to volunteer for 50 bugs.

Peter> I don't have a GNATS account yet, so I'm cc'ing this email to
Peter> overseers@gcc.gnu.org. My preferred login would be 'pbienst'.

Peter> Let's make this GCC release the most bug-free yet!

I don't want to make gnats-only accounts on this machine.
Doing so will lead to problems someday.

So could you fill out this form?
I'll make a real account, but I'll disable all logins (so that you
won't have cvs write access until the gcc maintainers decide
otherwise).

    http://sources.redhat.com/cgi-bin/pdw/ps_form.cgi

This of course presumes that the gcc maintainers want to give you
gnats write access.  That's up to them, not me.

Tom

  parent reply	other threads:[~2001-02-16 13:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010212160053S.mitchell@codesourcery.com>
2001-12-31 19:40 ` Peter Bienstman
2001-02-13  2:00   ` Peter Bienstman
2001-12-31 19:40   ` Tom Tromey [this message]
2001-02-16 13:19     ` Tom Tromey
2001-12-31 19:40     ` Mark Mitchell
2001-02-16 17:55       ` 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=87y9v65ncc.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Peter.Bienstman@rug.ac.be \
    --cc=mark@codesourcery.com \
    --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).