[rtems-docs commit] rsb: Move "History" to own chapter

[Sebastian Huber]

Module:    rtems-docs
Branch:    master
Commit:    633a24fc69b2ab5724fc00f6075b8f7baa43dd52
Changeset: http://git.rtems.org/rtems-docs/commit/?id=633a24fc69b2ab5724fc00f6075b8f7baa43dd52

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Thu Jan 10 12:52:23 2019 +0100

rsb: Move "History" to own chapter

Move it to the end of the document.  It is auxiliary information.

---

 rsb/history.rst        | 26 ++++++++++++++++++++++++++
 rsb/index.rst          | 23 ++++++++++++-----------
 rsb/source-builder.rst | 22 ----------------------
 3 files changed, 38 insertions(+), 33 deletions(-)

diff --git a/rsb/history.rst b/rsb/history.rst
new file mode 100644
index 0000000..2bb4324
--- /dev/null
+++ b/rsb/history.rst
@@ -0,0 +1,26 @@
+.. SPDX-License-Identifier: CC-BY-SA-4.0
+
+.. Copyright (C) 2012, 2016 Chris Johns <chrisj at rtems.org>
+
+
+History
+=======
+
+The RTEMS Source Builder is a stand alone tool based on another tool called the
+*SpecBuilder* written by Chris Johns. The *SpecBuilder* was written around 2010
+for the RTEMS project to provide Chris with a way to build tools on hosts that
+did not support RPMs. At the time the RTEMS tools maintainer only supported
+*spec* files and these files held all the vital configuration data needed to
+create suitable tool sets. The available SRPM and *spec* files by themselves
+where of little use because a suitable ``rpm`` tool was needed to use them. At
+the time the available versions of ``rpm`` for a number of non-RPM hosts were
+broken and randomly maintained. The solution Chris settled on was to use the
+*spec* files and to write a Python based tool that parsed the *spec* file
+format creating a shell script that could be run to build the package. The
+approach proved successful and Chris was able to track the RPM version of the
+RTEMS tools on a non-RPM host for a number of years.
+
+The *SpecBuilder* tool did not build tools or packages unrelated to the RTEMS
+Project where no suitable *spec* file was available so another tool was
+needed. Rather than start again Chris decided to take the parsing code for the
+*spec* file format and build a new tool called the RTEMS Source Builder.
diff --git a/rsb/index.rst b/rsb/index.rst
index 8edafe0..57e60ff 100644
--- a/rsb/index.rst
+++ b/rsb/index.rst
@@ -24,16 +24,17 @@ RTEMS Source Builder (|version|).
 .. include:: ../common/header.rst
 
 .. toctree::
-	:maxdepth: 5
-	:numbered:
-
-        source-builder
-        building-tools-and-rtems.rst
-	project-sets
-	cross-canadian-cross
-	third-party-packages
-	configuration
-	commands
-	bug-reporting
+    :maxdepth: 5
+    :numbered:
+
+    source-builder
+    building-tools-and-rtems.rst
+    project-sets
+    cross-canadian-cross
+    third-party-packages
+    configuration
+    commands
+    bug-reporting
+    history
 
 * :ref:`genindex`
diff --git a/rsb/source-builder.rst b/rsb/source-builder.rst
index 51a15f9..1da8275 100644
--- a/rsb/source-builder.rst
+++ b/rsb/source-builder.rst
@@ -133,28 +133,6 @@ own tool set that you install under your home directory. Avoiding installing
 any extra packages as a super user is always helpful in maintaining a secure
 computing environment.
 
-History
--------
-
-The RTEMS Source Builder is a stand alone tool based on another tool called the
-*SpecBuilder* written by Chris Johns. The *SpecBuilder* was written around 2010
-for the RTEMS project to provide Chris with a way to build tools on hosts that
-did not support RPMs. At the time the RTEMS tools maintainer only supported
-*spec* files and these files held all the vital configuration data needed to
-create suitable tool sets. The available SRPM and *spec* files by themselves
-where of little use because a suitable ``rpm`` tool was needed to use them. At
-the time the available versions of ``rpm`` for a number of non-RPM hosts were
-broken and randomly maintained. The solution Chris settled on was to use the
-*spec* files and to write a Python based tool that parsed the *spec* file
-format creating a shell script that could be run to build the package. The
-approach proved successful and Chris was able to track the RPM version of the
-RTEMS tools on a non-RPM host for a number of years.
-
-The *SpecBuilder* tool did not build tools or packages unrelated to the RTEMS
-Project where no suitable *spec* file was available so another tool was
-needed. Rather than start again Chris decided to take the parsing code for the
-*spec* file format and build a new tool called the RTEMS Source Builder.
-
 Controlling the Tools Build
 ---------------------------