From: Arnaud Charlet <charlet@adacore.com>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix warnings from including fdl.texi into gnat-style.texi
Date: Sun, 22 Feb 2015 18:04:00 -0000 [thread overview]
Message-ID: <20150222173714.GA3798@adacore.com> (raw)
In-Reply-To: <54E9F4D2.9050504@mentor.com>
> While generating gnat-style.info, we see these warnings:
> ...
> src/gcc/doc/include/fdl.texi:33: warning: node `Index' is next for
> `GNU Free Documentation License' in menu but not in sectioning
> src/gcc/doc/include/fdl.texi:33: warning: node `Top' is up for `GNU
> Free Documentation License' in menu but not in sectioning
> ...
>
> Attached patch fixes these.
>
> Ok for stage4?
The gnat-style.texi part is OK. I cannot approve the fdl part though.
Arno
next prev parent reply other threads:[~2015-02-22 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 15:36 Tom de Vries
2015-02-22 18:04 ` Arnaud Charlet [this message]
2015-03-20 10:11 ` Tom de Vries
2015-03-23 15:00 ` Gerald Pfeifer
2015-06-14 14:13 ` Tom de Vries
2015-08-24 15:18 ` [PING][PATCH] " Tom de Vries
2015-08-24 15:26 ` Arnaud Charlet
2015-12-08 9:13 ` [PATCH] " Tom de Vries
2015-12-08 18:10 ` Gerald Pfeifer
2015-12-08 20:26 ` Mike Stump
2015-12-14 8:37 ` Tom de Vries
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=20150222173714.GA3798@adacore.com \
--to=charlet@adacore.com \
--cc=Tom_deVries@mentor.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).