| 1 |
Most of the GLEPs never really followed the header order specified |
| 2 |
in GLEP 1, and there is no technical reason to enforce that. |
| 3 |
--- |
| 4 |
glep-0001.txt | 5 ++--- |
| 5 |
1 file changed, 2 insertions(+), 3 deletions(-) |
| 6 |
|
| 7 |
diff --git a/glep-0001.txt b/glep-0001.txt |
| 8 |
index 65bc37a..22787bf 100644 |
| 9 |
--- a/glep-0001.txt |
| 10 |
+++ b/glep-0001.txt |
| 11 |
@@ -235,9 +235,8 @@ GLEP Header |
| 12 |
|
| 13 |
Every GLEP has certain attributes associated with it. When a GLEP is sent |
| 14 |
to the mailing lists for discussion, it should begin with an RFC 2822 style |
| 15 |
-header preamble between two triple-dashed lines. The headers must appear |
| 16 |
-in the following order. Headers marked with "*" are optional. All other |
| 17 |
-headers are required. |
| 18 |
+header preamble between two triple-dashed lines. Headers marked with "*" are |
| 19 |
+optional. All other headers are required. |
| 20 |
|
| 21 |
:: |
| 22 |
|
| 23 |
-- |
| 24 |
2.14.1 |
Archives