Gentoo Archives: gentoo-project

From: "Michał Górny" <mgorny@g.o>
To: gentoo-project@l.g.o
Cc: "Michał Górny" <mgorny@g.o>
Subject: [gentoo-project] [PATCH 10/24] glep-0001: Require YAML conformance from the preamble
Date: Sun, 17 Sep 2017 20:25:54
Message-Id: 20170917202432.7763-11-mgorny@gentoo.org
In Reply to: [gentoo-project] [PATCHES v2] New old-school GLEP workflow (GLEP 1/2 update) by "Michał Górny"
1 Most of the GLEP headers can be parsed by a standard YAML parsers. There
2 are currently two exceptions to that (due to title starting with "),
3 and they are easy enough to fix. Therefore, require conformance with
4 YAML to make sure we do not have to reinvent header parsing.
5 ---
6 glep-0001.txt | 7 +++++--
7 1 file changed, 5 insertions(+), 2 deletions(-)
8
9 diff --git a/glep-0001.txt b/glep-0001.txt
10 index 5cc8264..e2bf430 100644
11 --- a/glep-0001.txt
12 +++ b/glep-0001.txt
13 @@ -228,8 +228,9 @@ GLEP Header
14 Every GLEP has certain attributes associated with it. When a GLEP is sent
15 to the mailing lists for discussion, it should begin with an RFC 2822 style
16 header preamble between two triple-dashed lines. The headers must appear
17 -in the following order. Headers marked with "*" are optional. All other
18 -headers are required.
19 +in the following order. For interoperability, the header preamble should also
20 +conform to the YAML standard [#YAML]_. Headers marked with "*" are optional.
21 +All other headers are required.
22
23 ::
24
25 @@ -371,6 +372,8 @@ References and Footnotes
26
27 .. [#GLEP2] http://glep.gentoo.org/glep-0002.html
28
29 +.. [#YAML] http://yaml.org/
30 +
31
32 Copyright
33 =========
34 --
35 2.14.1