[gentoo-commits] data/glep:glep-manifest commit in: /

["Michał Górny" <mgorny@gentoo.org>]

commit:     c20fe701388d8394c0e957177355eb139559c84e
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 13 15:09:38 2017 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Fri Oct 27 17:44:21 2017 +0000
URL:        https://gitweb.gentoo.org/data/glep.git/commit/?id=c20fe701

glep-0002: Indicate that the 'Replaces' header is multi-value

Update the description of the 'Replaces' header to account for
replacement of multiple GLEPs. This possibility is already permitted
by GLEP 1; however, GLEP 2 seems to be out of date.

Closes: https://bugs.gentoo.org/577760

 glep-0002.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/glep-0002.rst b/glep-0002.rst
index c73beec..be11dba 100644
--- a/glep-0002.rst
+++ b/glep-0002.rst
@@ -116,11 +116,11 @@ directions below.
   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.
-  is either Accepted, Final, or Rejected.  You aren't replacing an older open
-  GLEP if you're submitting a competing idea.
+- Add a Replaces header if your GLEP obsoletes one or more earlier GLEPs.
+  The value of this header is the numbers of the GLEPs that your new GLEP is
+  replacing, separated by commas.  Only add this header if the older GLEP is
+  in "final" form, i.e. is either Accepted, Final, or Rejected.  You aren't
+  replacing an older open GLEP if you're submitting a competing idea.
 
 - Now write your Abstract, Rationale, and other content for your GLEP,
   replacing all of this gobbledygook with your own text. Be sure to adhere to