From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>,
Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
gcc@gcc.gnu.org, bangerth@ices.utexas.edu,
giovannibajo@libero.it
Subject: Re: Suggested Bugzilla improvements
Date: Wed, 14 May 2003 15:07:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305141704190.58793@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.53.0305132148170.26146@kern.srcf.societies.cam.ac.uk>
Daniel,
here is some further information in addition to what Joseph wrote.
On Tue, 13 May 2003, Joseph S. Myers wrote:
>> I seem to have lost the message saying what other docs on the gcc
>> website i should update when it goes live.
>> Can someone give me the list again, if it's not too much trouble?
>> I'm not talking about Bugzilla's docs, i mean the gcc web pages.
> Everywhere on the website mentioning GNATS, as found by grep.
Most of that is gnats.html, which we should replace by a suitable page
for bugzilla (note that in bugs/ we have some further information on
our bug tracking effort, some of which we already generalized from GNATS),
and some references in bugs.html.
> Everywhere in the manual mentioning GNATS, likewise.
Wolfgang will soon commit a patch for the main manual, and already has
submitted one for the Fortran manual, so you can safely ignore these two.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-05-14 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 16:07 Volker Reichelt
2003-05-13 16:53 ` Daniel Berlin
2003-05-13 20:50 ` Joseph S. Myers
2003-05-14 15:07 ` Gerald Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 9:19 Volker Reichelt
2003-05-13 10:20 ` Joseph S. Myers
2003-05-13 14:39 ` Daniel Berlin
2003-05-13 14:52 ` Joseph S. Myers
2003-05-13 15:33 ` Daniel Berlin
2003-05-13 14:41 ` Daniel Berlin
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=Pine.BSF.4.55.0305141704190.58793@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=bangerth@ices.utexas.edu \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=jsm28@cam.ac.uk \
--cc=reichelt@igpm.rwth-aachen.de \
/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).