1 |
Sebastian Pipping posted on Thu, 26 Mar 2015 19:15:09 +0100 as excerpted: |
2 |
|
3 |
> Changes: |
4 |
> |
5 |
> * Revision bump |
6 |
|
7 |
This ^^.. |
8 |
|
9 |
> * Add section on .php.inc |
10 |
> |
11 |
> * Add thanks line |
12 |
> |
13 |
> |
14 |
> ================================================================ |
15 |
> Title: Apache AddHandler vulnerability protection |
16 |
> Author: Sebastian Pipping <sping@g.o> |
17 |
> Content-Type: text/plain |
18 |
> Posted: 2015-03-26 |
19 |
> Revision: 2 |
20 |
|
21 |
And this ^^.. |
22 |
|
23 |
> News-Item-Format: 1.0 |
24 |
> Display-If-Installed: www-servers/apache |
25 |
|
26 |
|
27 |
This is a common error. While not entirely intuitive, AFAIK revision is |
28 |
a post-publication value and should remain revision 1 unless a correction |
29 |
is needed once published. |
30 |
|
31 |
|
32 |
Perhaps it is time to formally change that. Reading software must be |
33 |
prepared to deal with first-seen values greater than 1 in any case, since |
34 |
a user might not have seen the original revision, and history has |
35 |
repeatedly demonstrated that people want to bump the revision number |
36 |
during initial discussion. So why not simply let it be bumped, and let |
37 |
the first published version be what it may? If necessary, further bumps |
38 |
can happen from there. |
39 |
|
40 |
Tho in practice, very likely as a result of the pre-publishing approval |
41 |
process including discussion here, AFAIK no such post-publishing |
42 |
correcting revision has ever been necessary. But that's not to say it |
43 |
won't /ever/ be necessary, so having the ability is certainly a good |
44 |
thing. =:^) |
45 |
|
46 |
|
47 |
Either that or start out with a pre-publishing version of 0.1 and bump |
48 |
that, changing it to 1 on initial publish. |
49 |
|
50 |
-- |
51 |
Duncan - List replies preferred. No HTML msgs. |
52 |
"Every nonfree program has a lord, a master -- |
53 |
and if you use the program, he is your master." Richard Stallman |