[gentoo-project] [PATCH 21/24] glep-0002: Rearrange paragraphs to reflect new ordering of headers.

[Michał Górny]

From: Ulrich Müller <ulm@g.o>

No other text changes.
---
 glep-0002.txt | 31 +++++++++++++++----------------
 1 file changed, 15 insertions(+), 16 deletions(-)

diff --git a/glep-0002.txt b/glep-0002.txt
index 6b8f830..ef1f0f0 100644
--- a/glep-0002.txt
+++ b/glep-0002.txt
@@ -80,34 +80,27 @@ directions below.
 
 - Change the Title header to the title of your GLEP.
 
-- Leave the Version and Last-Modified headers alone; we'll take care
-  of those when we check your GLEP into CVS.
-
 - Change the Author header to include your name, and optionally your
   email address.  Be sure to follow the format carefully: your name must
   appear first, and it must not be contained in parentheses.  Your email
   address may appear second (or it can be omitted) and if it appears, it must
   appear in angle brackets.
 
+- For Standards Track GLEPs, change the Type header to "Standards Track".
+
+- For Informational GLEPs, change the Type header to "Informational".
+
+- Change the Status header to "Draft".
+
+- Leave the Version and Last-Modified headers alone; we'll take care
+  of those when we check your GLEP into CVS.
+
 - If there is a forum thread or a mailing list for discussion 
   of your new feature, add a Discussions-To header right after the Author
   header.  You should not add a Discussions-To header if the mailing list to
   be used is gentoo-dev@g.o, or if discussions should be sent to you
   directly.  Most Informational GLEPs don't have a Discussions-To header.
 
-- Change the Status header to "Draft".
-
-- For Standards Track GLEPs, change the Type header to "Standards
-  Track".
-
-- For Informational GLEPs, change the Type header to "Informational".
-
-- For Standards Track GLEPs, if your feature depends on the acceptance
-  of some other currently in-development GLEP, add a Requires header right
-  after the Type header.  The value should be the GLEP number of the GLEP
-  yours depends on.  Don't add this header if your dependent feature is
-  described in a Final GLEP.
-
 - Change the Created header to today's date.  Be sure to follow the
   format carefully: it must be in ``dd-mmm-yyyy`` format, where the ``mmm`` is
   the 3 English letter month abbreviation, i.e. one of Jan, Feb, Mar, Apr,
@@ -123,6 +116,12 @@ directions below.
   You must manually add new dates and check them in.  If you don't have
   check-in privileges, send your changes to the GLEP editors.
 
+- For Standards Track GLEPs, if your feature depends on the acceptance
+  of some other currently in-development GLEP, add a Requires header right
+  after the Type header.  The value should be the GLEP number of the GLEP
+  yours depends on.  Don't add this header if your dependent feature is
+  described in a Final GLEP.
+
 - Add a Replaces header if your GLEP obsoletes an earlier GLEP.  The
   value of this header is the number of the GLEP that your new GLEP is
   replacing.  Only add this header if the older GLEP is in "final" form, i.e.
-- 
2.14.1