design.xml patch

John Davis <[email protected]>
Newsgroups gmane.linux.gentoo.installer
Organization Paul Davis Automation, Inc.
Message-ID <[email protected]>
Hi all -
I was cleaning up the releng directory per swift's email to -core about
cleanups to problems pages so that they can be printed. I fixed up
design.xml so that it is in accordance with all Gentoo XML guidelines,
but found that I don't have commit access. Please find attached the
patch to design.xml.

Cheers,
-- 
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>

----
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
Fingerprint: 4F9E 41F6 D072 5C1A 636C  2D46 B92C 4823 E281 41BB
design.xml.diff (text/x-patch, 3.5 KB)
--- design.xml.old	2004-09-17 10:55:57.405814976 -0400
+++ design.xml	2004-09-17 10:48:00.454322624 -0400
@@ -2,7 +2,7 @@
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<guide link="/gentoo-installer/installer-intro.xml">
+<guide link="design.xml">
 <title>Gentoo Linux Installer</title>
 
 <author title="Author">
@@ -12,19 +12,20 @@
   <mail link="[email protected]">Nicholas D. Wolfwood</mail>
 </author>
 
-<license/>
-
 <abstract>
 An introduction to the Gentoo Linux Installer project discussing it's purpose,
 design structure, and participants.
 </abstract>
 
+<license/>
+
 <version>1.0</version>
 <date>Jan 29, 2004</date>
 
 <chapter>
 <title>Overview</title>
 <section>
+<title>Overview</title>
 <body>
 
 <p>
@@ -53,6 +54,7 @@
 <chapter>
 <title>Features</title>
 <section>
+<title>Features</title>
 <body>
 
 <p>
@@ -65,6 +67,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Multiple front ends</title>
 <body>
@@ -80,6 +83,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Reusable back end framework</title>
 <body>
@@ -94,6 +98,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Automated deployment</title>
 <body>
@@ -109,6 +114,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Dry run profile generation</title>
 <body>
@@ -122,6 +128,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Full support for all Gentoo architectures</title>
 <body>
@@ -136,6 +143,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Specialized profiles</title>
 <body>
@@ -149,6 +157,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Open policies and standards use</title>
 <body>
@@ -162,6 +171,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Integration with future configuration projects</title>
 <body>
@@ -180,6 +190,7 @@
 <chapter>
 <title>Design and Structure</title>
 <section>
+<title>Design and Structure</title>
 <body>
 
 <p>
@@ -190,13 +201,14 @@
 
 <p>
 A few design requirements were stated:
+</p>
+
 <ul>
   <li>Multiple UIs must be supported (abstracted view support)</li>
   <li>A complete separation of model, view, and  control logic be kept</li>
   <li>All features must be supported regardless of front end or architecture</li>
   <li>Automated deployment always be possible</li>
 </ul>
-</p>
 
 <p>
 To this end, the installer platform (as the entire system is referenced) is
@@ -205,6 +217,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Front end (Client)</title>
 <body>
@@ -236,6 +249,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Back end (API or framework)</title>
 <body>
@@ -253,6 +267,7 @@
 <p>
 Since the framework is segregated from the client, it may be used for customized
 installation products developed by users. The major classes are as follows:
+</p>
 <ul>
   <li>
     A controller class that dictates, based on the architecture template (an XML
@@ -266,7 +281,6 @@
     deployment server for later use.
   </li>
 </ul>
-</p>
 
 <p>
 Other minor classes may be used for intermediary support, but these two solidify
@@ -275,6 +289,7 @@
 
 </body>
 </section>
+
 <section>
 <title>Deployment server</title>
 <body>
@@ -312,6 +327,7 @@
 <chapter>
 <title>Process</title>
 <section>
+<title>Process</title>
 <body>
 
 <p>
@@ -335,6 +351,7 @@
 <chapter>
 <title>Contact</title>
 <section>
+<title>Contact</title>
 <body>
 
 <p>
@@ -353,6 +370,7 @@
 <chapter>
 <title>Authors and Contributors</title>
 <section>
+<title>Authors and Contributors</title>
 <body>
 
 <p>
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBSv2BuSxII+KBQbsRAtdbAJ41yz7g5/5IAbs6TtggPvNb8HTOsACfXcML
xOTvyIyqJz94cT2QFNE/G8c=
=t6C0
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.