public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: Jason Molenda <jason@molenda.com>, overseers@sources.redhat.com
Subject: Re: a bit of gnatsweb info
Date: Mon, 31 Dec 2001 19:40:00 -0000	[thread overview]
Message-ID: <87bst38auj.fsf@creche.redhat.com> (raw)
In-Reply-To: <20010117173700.A9515@disaster.jaj.com>

>>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:

Phil> Would one of you kind gnatsd admins copy my entry ("pme") from
Phil> libstdc++'s gnatsd.access file to gcc's?

Done.

Tom

WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: Jason Molenda <jason@molenda.com>, overseers@sources.redhat.com
Subject: Re: a bit of gnatsweb info
Date: Fri, 19 Jan 2001 13:33:00 -0000	[thread overview]
Message-ID: <87bst38auj.fsf@creche.redhat.com> (raw)
Message-ID: <20010119133300._w8-d-KpeY4mQijKOSc29pVjYLMRHfsX9ZPM58zvG-s@z> (raw)
In-Reply-To: <20010117173700.A9515@disaster.jaj.com>

>>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:

Phil> Would one of you kind gnatsd admins copy my entry ("pme") from
Phil> libstdc++'s gnatsd.access file to gcc's?

Done.

Tom

  parent reply	other threads:[~2001-12-31 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31 19:40 Phil Edwards
2001-01-17 12:55 ` Phil Edwards
2001-12-31 19:40 ` Jason Molenda
2001-01-17 13:15   ` Jason Molenda
2001-12-31 19:40   ` Phil Edwards
2001-01-17 14:27     ` Phil Edwards
2001-12-31 19:40     ` Jason Molenda
2001-01-17 14:36       ` Jason Molenda
2001-12-31 19:40     ` Tom Tromey [this message]
2001-01-19 13:33       ` Tom Tromey
2001-12-31 19:40 ` Gerald Pfeifer
2001-01-17 13:57   ` 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=87bst38auj.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=jason@molenda.com \
    --cc=overseers@sources.redhat.com \
    --cc=pedwards@disaster.jaj.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).