From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] docs/grub-dev.texi: Fix out of place @itemize and fix makeinfo warnings
Date: Sat, 06 Apr 2013 22:11:26 +0200 [thread overview]
Message-ID: <5160816E.5020405@gmail.com> (raw)
In-Reply-To: <B9655C5E-7326-4CE2-A82F-CA1CD41D435A@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On 06.04.2013 21:58, Bryan Hundven wrote:
> On Apr 6, 2013, at 12:49 PM, Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> wrote:
>
>> On 04.04.2013 22:19, Bryan Hundven wrote:
>>
>>> In @node Bitmap_API, @itemize is not in the @subsection, and causes makeinfo to return 1.
>>
>> I wasn't able to reproduce this. At all.
>
> I got this issue with texinfo-5.1. If I move this @itemize after the @subsection, the build for grub completes for me.
> Maybe previous version of makeinfo are less lenient on the placement of @itemize?
>
Upgrading to 5.1 made this problem appear here as well
>>> Fix this and move sections in the texi to match the menu order to get rid of the warnings.
>>>
>>
>> It's better to change menu to match, than the other way round.
>
> Ok.
>
Can you preapre the patch for it, so I'll commit it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2013-04-06 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 20:19 [PATCH] docs/grub-dev.texi: Fix out of place @itemize and fix makeinfo warnings Bryan Hundven
2013-04-06 19:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-06 19:58 ` Bryan Hundven
2013-04-06 20:01 ` Bryan Hundven
2013-04-06 20:11 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-04-06 20:13 ` Bryan Hundven
2013-04-06 20:41 ` Bryan Hundven
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=5160816E.5020405@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.