[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-project
Subject:    [gentoo-project] [PATCH 09/24] glep-0001: Require --- around preamble for interoperability
From:       Michał Górny <mgorny () gentoo ! org>
Date:       2017-09-17 20:24:17
Message-ID: 20170917202432.7763-10-mgorny () gentoo ! org
[Download RAW message or body]

---
 glep-0001.txt | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/glep-0001.txt b/glep-0001.txt
index 9e585f5..5cc8264 100644
--- a/glep-0001.txt
+++ b/glep-0001.txt
@@ -227,9 +227,13 @@ GLEP Header
 
 Every GLEP has certain attributes associated with it. When a GLEP is sent
 to the mailing lists for discussion, it should begin with an RFC 2822 style
-header preamble.  The headers must appear in the following order.  Headers
-marked with "*" are optional. All other headers are required. ::
+header preamble between two triple-dashed lines.  The headers must appear
+in the following order.  Headers marked with "*" are optional. All other
+headers are required.
 
+::
+
+    ---
     GLEP: <glep number>
     Version: <major>[.<minor>]
     Last-Modified: <date of last update>
@@ -244,6 +248,7 @@ marked with "*" are optional. All other headers are required. ::
   * Requires: <glep numbers>
   * Replaces: <glep number>
   * Replaced-By: <glep number>
+    ---
 
 The Version field specifies the current version of the GLEP. The Version
 consists of a major version, optionally followed by a minor version (if
-- 
2.14.1



[prev in list] [next in list] [prev in thread] [next in thread]