From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Martin von Loewis <loewis@informatik.hu-berlin.de>
Cc: egcs@cygnus.com
Subject: FAQ vs Known Bugs List vs .texi Docs
Date: Fri, 06 Nov 1998 04:27:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.9811052359560.27916-100000@alphard.dbai.tuwien.ac.at> (raw)
In-Reply-To: <199811050926.KAA09474@pandora>
On Thu, 5 Nov 1998, Martin von Loewis wrote:
> P.S. Even though this came up the first time, I propose to add it to
> the FAQ ("Why does bad_exception not work?") or as a non-bug to the
> "Known bugs list".
I believe we should not add too much the FAQ (especially non-FAQs), but
I'd be willing to accept that for the "Known bugs list", if you submit
a patch.
In general, though, what about the .texi documentation? There is a special
section about bugs and non-bugs. Shouldn't stuff like that go there as
well? Or only there?
We could put the .texi documentation on the web and link that part.
Just an idea...
Gerald
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
prev parent reply other threads:[~1998-11-06 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-22 5:33 Troubles with exception specification Ryszard Kabatek
1998-11-05 5:10 ` Martin von Loewis
1998-11-06 4:27 ` Gerald Pfeifer [this message]
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.GSO.4.05.9811052359560.27916-100000@alphard.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=egcs@cygnus.com \
--cc=loewis@informatik.hu-berlin.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).