| 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 2112d41..78e76ce 100644 |
| 11 |
--- a/glep-0001.txt |
| 12 |
+++ b/glep-0001.txt |
| 13 |
@@ -236,8 +236,9 @@ GLEP Header |
| 14 |
|
| 15 |
Every GLEP has certain attributes associated with it. When a GLEP is sent |
| 16 |
to the mailing lists for discussion, it should begin with an RFC 2822 style |
| 17 |
-header preamble between two triple-dashed lines. Headers marked with "*" are |
| 18 |
-optional. All other headers are required. |
| 19 |
+header preamble between two triple-dashed lines. For interoperability, |
| 20 |
+the header preamble should also conform to the YAML standard [#YAML]_. |
| 21 |
+Headers marked with "*" are optional. All other headers are required. |
| 22 |
|
| 23 |
:: |
| 24 |
|
| 25 |
@@ -379,6 +380,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 |
Archives