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 06/24] glep-0001: Clarify the process on updating Replaced-By
Date: Sun, 17 Sep 2017 20:25:14
Message-Id: 20170917202432.7763-7-mgorny@gentoo.org
In Reply to: [gentoo-project] [PATCHES v2] New old-school GLEP workflow (GLEP 1/2 update) by "Michał Górny"
1 Indicate that the GLEPs should not be replaced until the replacement
2 GLEP is accepted.
3 ---
4 glep-0001.txt | 8 ++++----
5 1 file changed, 4 insertions(+), 4 deletions(-)
6
7 diff --git a/glep-0001.txt b/glep-0001.txt
8 index 82cc8f2..301a4b4 100644
9 --- a/glep-0001.txt
10 +++ b/glep-0001.txt
11 @@ -285,10 +285,10 @@ posted to gentoo-dev. All three headers should be in dd-mmm-yyyy format, e.g.
12 GLEPs may have a Requires header, indicating the GLEP numbers that this GLEP
13 depends on.
14
15 -GLEPs may also have a Replaced-By header indicating that a GLEP has been
16 -rendered obsolete by a later document; the value is the number of the GLEP
17 -that replaces the current document. The newer GLEP must have a Replaces
18 -header containing the number of the GLEP that it rendered obsolete.
19 +GLEPs may also have a Replaces header indicating that a GLEP is meant
20 +to replace one or more older GLEPs. Once such a GLEP is accepted, a matching
21 +Replaced-By should be added to all replaced GLEPs and their status should
22 +be updated to Replaced.
23
24
25 Reporting GLEP Bugs, or Submitting GLEP Updates
26 --
27 2.14.1