public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bje@gcc.gnu.org
To: bje@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, simon@pushface.org
Subject: Re: ada/9406: Documentation suggestion
Date: Tue, 18 Feb 2003 12:09:00 -0000 [thread overview]
Message-ID: <20030218120931.17395.qmail@sources.redhat.com> (raw)
Synopsis: Documentation suggestion
Responsible-Changed-From-To: unassigned->bje
Responsible-Changed-By: bje
Responsible-Changed-When: Tue Feb 18 12:09:30 2003
Responsible-Changed-Why:
I'll take it.
State-Changed-From-To: open->analyzed
State-Changed-By: bje
State-Changed-When: Tue Feb 18 12:09:30 2003
State-Changed-Why:
Looks reasonable to me.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9406
next reply other threads:[~2003-02-18 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 12:09 bje [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 14:16 Ben Elliston
2003-02-23 14:56 Geert Bosch
2003-02-23 12:26 Simon Wright
2003-02-20 22:46 Geert Bosch
2003-02-20 21:46 Simon Wright
2003-02-19 20:56 bosch
2003-02-18 14:06 bje
2003-01-22 20:56 simon
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=20030218120931.17395.qmail@sources.redhat.com \
--to=bje@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=simon@pushface.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).