Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] docs/manual: limit the depth of the TOC in the HTML output
Date: Tue, 03 Dec 2013 12:20:03 +0100	[thread overview]
Message-ID: <87d2lenpuk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <e2932a94718affcd5ec7dd1c4cbb4cb8c140340c.1386017298.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Mon, 2 Dec 2013 21:49:27 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > The current TOC level is set to 4, which does not mean 'a 4-level deep TOC',
 > but really means 'a TOC deep to the 4th level', with the first level being
 > level 0, which means we have:

 >     12. Appendix
 >         12.1. Makedev syntax documentation
 >         12.2. Makeuser syntax documentation
 >         12.3. Partition table layout description syntax
 >             12.3.1. The global section
 >                 Properties for the global section

 > Which a bit too much. And yet, the fifth level is not shown, since we
 > don't have any! :-/

 > Limit the depth of the TOC to three levels, which is just enough to be
 > usefull, yet not cluttered by low-level titles.

 > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-12-03 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 20:49 [Buildroot] [pull request] Pull request for branch yem/misc Yann E. MORIN
2013-12-02 20:49 ` [Buildroot] [PATCH 1/2] docs/manual: limit the depth of the TOC in the HTML output Yann E. MORIN
2013-12-03 11:20   ` Peter Korsgaard [this message]
2013-12-02 20:49 ` [Buildroot] [PATCH 2/2] package/rpi-firmware: only install one firmware file Yann E. MORIN
2013-12-03 11:20   ` Peter Korsgaard

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=87d2lenpuk.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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