From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [v3] Update C++11 status table.
Date: Thu, 09 Feb 2012 18:56:00 -0000 [thread overview]
Message-ID: <CAH6eHdTAki99ikRAVetrHZtkgk5uMzfuX41nkcQ0Z9arbPkF=Q@mail.gmail.com> (raw)
In-Reply-To: <20120209094341.7c6e251d@shotwell>
On 9 February 2012 17:43, Benjamin Kosnik wrote:
>
>> * doc/xml/manual/documentation_hacking.xml: Fix invalid
>> attribute.
>>
>> Also committed to trunk. Tested with 'make doc-xml-validate-docbook
>> doc-html'
>
> Doh!
>
> Thanks for cleaning up after my late-night hacking..... If you can, I'd
> appreciate you trying to generate the PDF doxygen manual with the
> memory-increasing change to TeX. I understand the doc toolchain for
> doing this is non-trivial.
Sure, I'll give it a go later.
next prev parent reply other threads:[~2012-02-09 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 0:07 Jonathan Wakely
2012-02-09 1:42 ` Jonathan Wakely
2012-02-09 17:44 ` Benjamin Kosnik
2012-02-09 18:56 ` Jonathan Wakely [this message]
2012-06-14 20:59 Jonathan Wakely
2012-10-19 16:57 [v3] update " Jonathan Wakely
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='CAH6eHdTAki99ikRAVetrHZtkgk5uMzfuX41nkcQ0Z9arbPkF=Q@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=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).