public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: jsm28@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: web/973
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <20010122110600.5261.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR web/973; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <gerald@gcc.gnu.org>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: web/973
Date: Mon, 22 Jan 2001 10:56:19 +0000 (GMT)
On 22 Jan 2001 gerald@gcc.gnu.org wrote:
> Joseph offered to take care of this once he has appropriate
> write access, which should be the case now according to Jeff.
I've cleaned some parts up, but fully polishing the whole FAQ has been
left pending any resolution of whether we want to continue using the FOM
or whether we should go back to a manually maintained FAQ with memorable
URLs and better quality control.
--
Joseph S. Myers
jsm28@cam.ac.uk
>From lerdsuwa@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: lerdsuwa@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2201
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010313122604.29084.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02286.html
Content-length: 535
The following reply was made to PR c++/2201; it has been noted by GNATS.
From: lerdsuwa@gcc.gnu.org
To: a.metselaar@math.utwente.nl, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/2201
Date: 13 Mar 2001 12:24:48 -0000
Synopsis: Internal compiler error while compiling patr of lapack++
State-Changed-From-To: open->closed
State-Changed-By: lerdsuwa
State-Changed-When: Tue Mar 13 04:24:47 2001
State-Changed-Why:
Fixed in the CVS.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2201&database=gcc
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 0:00 Joseph S. Myers [this message]
2001-06-06 10:06 web/973 jsm28
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=20010122110600.5261.qmail@sourceware.cygnus.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=jsm28@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).