From: Benjamin Kosnik <bkoz@redhat.com>
To: libstdc++@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: [v3] doxygen updates
Date: Wed, 29 Nov 2006 14:17:00 -0000 [thread overview]
Message-ID: <20061129151614.135fe0da.bkoz@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
Updates to the "latest" doxygen and changes in style of generated
pages to more explicit qualification. More coherent namespace
documentation. Some of the css formatting for the class member
documentation seems off, which is next on the to-do list.
Newer graphviz has improved (cairo) output.
As here:
http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen
tested x86/linux
-benjamin
[-- Attachment #2: p.20061129.bz2 --]
[-- Type: application/x-bzip2, Size: 16754 bytes --]
next reply other threads:[~2006-11-29 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 14:17 Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 10:48 Benjamin Kosnik
2008-03-26 8:05 Benjamin Kosnik
2008-03-26 8:05 ` Benjamin Kosnik
2004-11-05 20:01 Benjamin Kosnik
2004-11-07 6:20 ` Joe Buck
2004-11-08 16:02 ` Phil Edwards
2004-11-08 16:24 ` Benjamin Kosnik
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=20061129151614.135fe0da.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).