Gentoo Archives: gentoo-dev

From: James Le Cuirot <chewi@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/
Date: Thu, 05 Sep 2019 19:28:34
Message-Id: 20190905202814.0bc424d5@symphony.aura-online.co.uk
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/ by Kent Fredric
1 On Fri, 6 Sep 2019 07:26:42 +1200
2 Kent Fredric <kentnl@g.o> wrote:
3
4 > On Thu, 5 Sep 2019 09:04:23 -0500
5 > Gordon Pettey <petteyg359@×××××.com> wrote:
6 >
7 > > You'll note the bit you quoted in defense of skipping review says
8 > > "changes", and the bit about new eclasses says "do not skip this step".
9 >
10 > Emphasis added:
11 >
12 > -----
13 > BEFORE committing a NEW eclass to the tree, it SHOULD be emailed to the
14 > gentoo-dev mailing list with a justification and a proposed
15 > implementation. DO NOT SKIP this step — sometimes a better
16 > implementation or an alternative which does not require a new eclass
17 > will be suggested.
18 > -----
19 >
20 >
21 > If its mandatory, it must say "MUST" not "SHOULD", SHOULD is a
22 > suggestion, following a suggestion with an imperative just adds
23 > predictable confusion.
24 >
25 > Either fix the "should", or drop the "DO NOT SKIP".
26 >
27 > Otherwise you're just giving mixed messages.
28
29 +1
30
31 --
32 James Le Cuirot (chewi)
33 Gentoo Linux Developer