1 |
On Tue, 2005-12-13 at 21:38 +0000, Ciaran McCreesh wrote: |
2 |
> On Tue, 13 Dec 2005 22:18:36 +0100 Jakub Moc <jakub@g.o> wrote: |
3 |
> | Pardon my ignorance, but how's a GLEP amending a GLEP (amending a |
4 |
> | GLEP ...) less confusing than just changing the text of the original |
5 |
> | GLEP... Huh, goes beyond me... |
6 |
> |
7 |
> History. Look at RFCs for a good example. There's nothing wrong with |
8 |
> extending or replacing parts of existing standards, especially if the |
9 |
> existing standards are clearly marked as "extended by $blah" or |
10 |
> "replaced by $blah". On the other hand, changing accepted GLEPs leads to |
11 |
> confusion -- when someone says "GLEP 1", do they mean "GLEP 1 as it was |
12 |
> when it was approved" or "GLEP 1 plus the modifications made three |
13 |
> weeks ago" or "GLEP 1 plus the modifications made three weeks ago plus |
14 |
> the modifications made last Tuesday"? |
15 |
> |
16 |
> Plus, of course, it helps to have a record of *why* changes were |
17 |
> made... |
18 |
> |
19 |
Or IEEE ish |
20 |
|
21 |
Original: GLEP 01 |
22 |
Ammended: GLEP 01.a |
23 |
-- |
24 |
Lares Moreau <lares.moreau@×××××.com> | LRU: 400755 http://counter.li.org |
25 |
lares/irc.freenode.net | |
26 |
Gentoo x86 Arch Tester | ::0 Alberta, Canada |
27 |
Public Key: 0D46BB6E @ subkeys.pgp.net | Encrypted Mail Preferred |
28 |
Key fingerprint = 0CA3 E40D F897 7709 3628 C5D4 7D94 483E 0D46 BB6E |