[gentoo-pms] [PATCH] Rearrange front matter.

[Ulrich Müller]

---
 credits.tex      | 26 +++-----------------------
 introduction.tex | 23 +++++++++++++++++++++++
 pms.tex          |  4 ++--
 3 files changed, 28 insertions(+), 25 deletions(-)

diff --git a/credits.tex b/credits.tex
index 336ec51..3c98e91 100644
--- a/credits.tex
+++ b/credits.tex
@@ -1,3 +1,6 @@
+\thispagestyle{empty}
+\vspace*{\fill}
+
 \section*{Acknowledgements}
 
 Thanks to Mike Kelly (package manager provided utilities, section~\ref{sec:pkg-mgr-commands}),
@@ -15,29 +18,6 @@ inclusion.
 This document is released under the Creative Commons Attribution-Share Alike 3.0 Licence. The full
 text of this licence can be found at \url{http://creativecommons.org/licenses/by-sa/3.0/}.
 
-\section*{Reporting Issues}
-
-Issues (inaccuracies, wording problems, omissions etc.)\ in this document should be reported via
-Gentoo Bugzilla using product \e{Gentoo Hosted Projects}, component \e{PMS/EAPI} and the default
-assignee. There should be one bug per issue, and one issue per bug.
-
-Patches (in \t{git format-patch} form if possible) may be submitted either via Bugzilla or to the
-\t{gentoo-pms@l.g.o} mailing list. Patches will be reviewed by the PMS team, who will do
-one of the following:
-
-\begin{compactitem}
-\item Accept and apply the patch.
-\item Explain why the patch cannot be applied as-is. The patch may then be updated and resubmitted
-if \mbox{appropriate}.
-\item Reject the patch outright.
-\item Take special action merited by the individual circumstances.
-\end{compactitem}
-
-When reporting issues, remember that this document is not the appropriate place for pushing
-through changes to the tree or the package manager, except where those changes are bugs.
-
-If any issue cannot be resolved by the PMS team, it may be escalated to the Gentoo Council.
-
 % vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en :
 
 %%% Local Variables:
diff --git a/introduction.tex b/introduction.tex
index 7c22fd4..282fd18 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -25,6 +25,29 @@ ebuild repository looks like, and how an ebuild is allowed to behave. Thus, both
 package managers can change aspects of their behaviour not defined here without worry of
 incompatibilities with any particular repository.
 
+\section{Reporting Issues}
+
+Issues (inaccuracies, wording problems, omissions etc.)\ in this document should be reported via
+Gentoo Bugzilla using product \e{Gentoo Hosted Projects}, component \e{PMS/EAPI} and the default
+assignee. There should be one bug per issue, and one issue per bug.
+
+Patches (in \t{git format-patch} form if possible) may be submitted either via Bugzilla or to the
+\t{gentoo-pms@l.g.o} mailing list. Patches will be reviewed by the PMS team, who will do
+one of the following:
+
+\begin{compactitem}
+\item Accept and apply the patch.
+\item Explain why the patch cannot be applied as-is. The patch may then be updated and resubmitted
+if appropriate.
+\item Reject the patch outright.
+\item Take special action merited by the individual circumstances.
+\end{compactitem}
+
+When reporting issues, remember that this document is not the appropriate place for pushing
+through changes to the tree or the package manager, except where those changes are bugs.
+
+If any issue cannot be resolved by the PMS team, it may be escalated to the Gentoo Council.
+
 \section{Conventions}
 
 Text in \t{teletype} is used for filenames or variable names. \i{Italic} text is used for terms
diff --git a/pms.tex b/pms.tex
index c96fc05..9ca363c 100644
--- a/pms.tex
+++ b/pms.tex
@@ -27,13 +27,13 @@
 \begin{document}
 \maketitle
 
+\include{credits}
+
 \tableofcontents
 \listofalgorithms
 \listoflistings
 \listoftables
 
-\include{credits}
-
 \include{introduction}
 
 \include{eapis}
-- 
2.6.3