Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/11] RFC: Manual content reorganization
Date: Sun, 25 Mar 2012 23:50:07 +0200	[thread overview]
Message-ID: <201203252350.08283.arnout@mind.be> (raw)
In-Reply-To: <1332285001-12881-1-git-send-email-s.martin49@gmail.com>

On Wednesday 21 March 2012 00:09:50 Samuel MARTIN wrote:
> Right now, I'm not happy with everything I did.
> For example, now I use a deeper toc (4 title levels in this patch set vs. 3 on
> the current git master). This has a side effect on the html manual, indeed the
> toc only shows the first two level, this reduce the readability, IOW the fact
> that one can quickly find the relevant piece of information he/she is looking
> for.

 I don't think it reduces readability.  The table of contents is much 
clearer than it was before and more levels would just add clutter.  The
lack of hyperlinks to levels 3 and 4 also doesn't hurt because the
deepest levels are pretty short.  As you can see in the PDF: all level-2
sections fit on two pages, except for "Adding new packages to Buildroot".


 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2012-03-25 21:50 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 23:09 [Buildroot] [PATCH 00/11] RFC: Manual content reorganization Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 01/11] manual: rework the whole documentation stub Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 02/11] manual: rework introduction.txt and update embedded-basics.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 03/11] manual: update prerequisite.txt Samuel MARTIN
2012-03-20 23:29   ` Thomas Petazzoni
2012-03-20 23:09 ` [Buildroot] [PATCH 04/11] manual: rework using.txt and update common-usage.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 05/11] manual: update make-tips.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 06/11] manual: update working-with.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 07/11] manual: update troubleshooting.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 08/11] manual: rework the intro of customize-rootfs.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 09/11] manual: update writing-rules.txt Samuel MARTIN
2012-03-20 23:10 ` [Buildroot] [PATCH 10/11] manual: update get-involved.txt Samuel MARTIN
2012-03-20 23:10 ` [Buildroot] [PATCH 11/11] manual: update contribute.txt Samuel MARTIN
2012-03-25 21:50 ` Arnout Vandecappelle [this message]
2012-04-15 10:56 ` [Buildroot] [PATCH 00/11] RFC: Manual content reorganization Samuel Martin
2012-04-25 20:23   ` Samuel Martin
2012-04-28 14:41     ` Arnout Vandecappelle
2012-05-06 21:04       ` Peter Korsgaard
2012-05-07 15:39         ` Samuel Martin
2012-05-12 23:18           ` Arnout Vandecappelle
2012-05-13 10:38             ` [Buildroot] [PATCH v2 " Samuel Martin
2012-05-13 10:38               ` [Buildroot] [PATCH v2 01/11] manual: rework the whole documentation stub Samuel Martin
2012-05-16 11:45                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 02/11] manual: rework introduction.txt and add embedded-basics.txt Samuel Martin
2012-05-16 11:50                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 03/11] manual: add prerequisite.txt Samuel Martin
2012-05-16 16:32                 ` Thomas De Schampheleire
2012-05-16 21:45                   ` Samuel Martin
2012-05-17  6:53                     ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 04/11] manual: rework using.txt and update common-usage.txt Samuel Martin
2012-05-16 16:47                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 05/11] manual: add make-tips.txt Samuel Martin
2012-05-16 16:55                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 06/11] manual: update working-with.txt Samuel Martin
2012-05-16 17:00                 ` Thomas De Schampheleire
2012-05-17 10:02                   ` Samuel Martin
2012-05-13 10:38               ` [Buildroot] [PATCH v2 07/11] manual: rework the intro of customize-rootfs.txt Samuel Martin
2012-05-16 17:02                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 08/11] manual: add troubleshooting.txt Samuel Martin
2012-05-16 17:04                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 09/11] manual: add writing-rules.txt Samuel Martin
2012-05-13 14:12                 ` Yegor Yefremov
2012-05-16 17:15                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 10/11] manual: add get-involved.txt Samuel Martin
2012-05-13 11:25                 ` Yegor Yefremov
2012-05-16 17:21                 ` Thomas De Schampheleire
2012-05-13 10:38               ` [Buildroot] [PATCH v2 11/11] manual: add contribute.txt Samuel Martin
2012-05-13 12:16                 ` Yegor Yefremov
2012-05-16 17:24                 ` Thomas De Schampheleire
2012-08-01 20:43 ` [Buildroot] [PATCH 00/11] RFC: Manual content reorganization Thomas Petazzoni
2012-08-05 14:59   ` Samuel Martin
2012-11-09 21:25 ` Arnout Vandecappelle
2012-11-09 22:45   ` Samuel Martin

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=201203252350.08283.arnout@mind.be \
    --to=arnout@mind.be \
    --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