From: Richard Biener <richard.guenther@gmail.com>
To: Arnaud Charlet <charlet@adacore.com>
Cc: Tom de Vries <Tom_deVries@mentor.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Ada] convert GNAT doc to sphinx
Date: Wed, 25 Feb 2015 12:02:00 -0000 [thread overview]
Message-ID: <CAFiYyc1GvEf7W6u4wC+z6QOuG=PbJOZakZCX8mHyTk1xKQuDFQ@mail.gmail.com> (raw)
In-Reply-To: <20150222191525.GA6460@adacore.com>
On Sun, Feb 22, 2015 at 8:15 PM, Arnaud Charlet <charlet@adacore.com> wrote:
>> Your patch removes these arguments to dircategory:
>> ...
>> $ git show bf5dffd3a47fe12ace71fe48e87cfb1b9ada1344 | grep dircategory
>> +@dircategory
>> -@dircategory GNU Ada tools
>> -@dircategory GNU Ada tools
>> +@dircategory
>> ...
>
> Well OK but these are automatically generated now, and this doesn't really
> answer my question about the documentation of @dircategory.
>
> I'll put a kludge for now to work around this. In the long term, if we could
> transition all docs to sphinx and get rid of texinfo that would be great.
I also see nonsensical @direntry - just compare to what is there on the
4.9 branch.
Richard.
> Arno
next prev parent reply other threads:[~2015-02-25 11:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 9:26 Arnaud Charlet
2015-02-22 17:37 ` Tom de Vries
2015-02-22 18:30 ` Arnaud Charlet
2015-02-22 19:02 ` Tom de Vries
2015-02-22 19:35 ` Arnaud Charlet
2015-02-22 20:48 ` Tom de Vries
2015-02-23 2:28 ` Arnaud Charlet
2015-02-23 8:26 ` Tom de Vries
2015-02-25 12:02 ` Richard Biener [this message]
2015-02-25 11:05 ` Joseph Myers
2015-02-25 11:27 ` Arnaud Charlet
2015-02-25 11:35 ` Joseph Myers
2015-02-25 11:40 ` Arnaud Charlet
2015-02-25 15:43 ` Joseph Myers
2015-02-25 15:50 ` Arnaud Charlet
2015-02-25 16:00 ` Joseph Myers
2015-02-26 17:18 ` David Malcolm
2015-02-26 17:26 ` Arnaud Charlet
2015-02-26 18:33 ` Mike Stump
2015-03-03 10:42 ` Matthias Klose
2015-03-03 13:33 ` Arnaud Charlet
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='CAFiYyc1GvEf7W6u4wC+z6QOuG=PbJOZakZCX8mHyTk1xKQuDFQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=Tom_deVries@mentor.com \
--cc=charlet@adacore.com \
--cc=gcc-patches@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).