From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 3 for 2014.08] manual: file organization: avoid unnecessary indirection
Date: Wed, 20 Aug 2014 21:39:53 +0200 [thread overview]
Message-ID: <acb3fb4cda4ff1fa58f4.1408563593@localhost> (raw)
In-Reply-To: <patchbomb.1408563591@localhost>
Some source files of the manual merely contain inclusion of other files.
Especially at top-level this is unnecessary, and one could just as well add
these includes in manual.txt.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
docs/manual/developer-guide.txt | 12 ------------
docs/manual/manual.txt | 24 +++++++++++++++++++++---
docs/manual/starting-up.txt | 9 ---------
docs/manual/working-with.txt | 13 -------------
4 files changed, 21 insertions(+), 37 deletions(-)
diff --git a/docs/manual/developer-guide.txt b/docs/manual/developer-guide.txt
deleted file mode 100644
--- a/docs/manual/developer-guide.txt
+++ /dev/null
@@ -1,12 +0,0 @@
-// -*- mode:doc; -*-
-// vim: set syntax=asciidoc:
-
-include::writing-rules.txt[]
-
-include::adding-packages.txt[]
-
-include::patch-policy.txt[]
-
-include::download-infra.txt[]
-
-include::debugging-buildroot.txt[]
diff --git a/docs/manual/manual.txt b/docs/manual/manual.txt
--- a/docs/manual/manual.txt
+++ b/docs/manual/manual.txt
@@ -20,13 +20,23 @@
include::introduction.txt[]
-include::starting-up.txt[]
+include::prerequisite.txt[]
+
+include::getting.txt[]
+
+include::using.txt[]
include::get-involved.txt[]
= User guide
-include::working-with.txt[]
+include::configure.txt[]
+
+include::configure-other-components.txt[]
+
+include::common-usage.txt[]
+
+include::customize.txt[]
include::faq-troubleshooting.txt[]
@@ -40,7 +50,15 @@
include::how-buildroot-works.txt[]
-include::developer-guide.txt[]
+include::writing-rules.txt[]
+
+include::adding-packages.txt[]
+
+include::patch-policy.txt[]
+
+include::download-infra.txt[]
+
+include::debugging-buildroot.txt[]
include::contribute.txt[]
diff --git a/docs/manual/starting-up.txt b/docs/manual/starting-up.txt
deleted file mode 100644
--- a/docs/manual/starting-up.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-// -*- mode:doc; -*-
-// vim: set syntax=asciidoc:
-
-include::prerequisite.txt[]
-
-include::getting.txt[]
-
-include::using.txt[]
-
diff --git a/docs/manual/working-with.txt b/docs/manual/working-with.txt
deleted file mode 100644
--- a/docs/manual/working-with.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-// -*- mode:doc; -*-
-// vim: set syntax=asciidoc:
-
-This section explains how you can customize Buildroot to fit your
-needs.
-
-include::configure.txt[]
-
-include::configure-other-components.txt[]
-
-include::common-usage.txt[]
-
-include::customize.txt[]
next prev parent reply other threads:[~2014-08-20 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 19:39 [Buildroot] [PATCH 0 of 3 for 2014.08] Manualimprovements part 3 Thomas De Schampheleire
2014-08-20 19:39 ` [Buildroot] [PATCH 1 of 3 for 2014.08] manual/user guide: rework 'Configuration of other components' chapter Thomas De Schampheleire
2014-08-20 19:39 ` Thomas De Schampheleire [this message]
2014-08-20 19:39 ` [Buildroot] [PATCH 3 of 3 for 2014.08] manual: file organization: rename files to match new section title Thomas De Schampheleire
2014-08-21 13:41 ` [Buildroot] [PATCH 0 of 3 for 2014.08] Manualimprovements part 3 Thomas Petazzoni
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=acb3fb4cda4ff1fa58f4.1408563593@localhost \
--to=patrickdepinguin@gmail.com \
--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