public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Review: Apache AddHandler news item
Date: Fri, 27 Mar 2015 02:33:39 +0000 (UTC)	[thread overview]
Message-ID: <pan$330d9$abb55956$eb57e62d$59b09efa@cox.net> (raw)
In-Reply-To: 55144CAD.1040901@gentoo.org

Sebastian Pipping posted on Thu, 26 Mar 2015 19:15:09 +0100 as excerpted:

> Changes:
> 
>  * Revision bump

This ^^..
 
>  * Add section on .php.inc
> 
>  * Add thanks line
> 
> 
> ================================================================
> Title: Apache AddHandler vulnerability protection
> Author: Sebastian Pipping <sping@gentoo.org>
> Content-Type: text/plain
> Posted: 2015-03-26
> Revision: 2

And this ^^..

> News-Item-Format: 1.0
> Display-If-Installed: www-servers/apache


This is a common error.  While not entirely intuitive, AFAIK revision is 
a post-publication value and should remain revision 1 unless a correction 
is needed once published.


Perhaps it is time to formally change that.  Reading software must be 
prepared to deal with first-seen values greater than 1 in any case, since 
a user might not have seen the original revision, and history has 
repeatedly demonstrated that people want to bump the revision number 
during initial discussion.  So why not simply let it be bumped, and let 
the first published version be what it may?  If necessary, further bumps 
can happen from there.

Tho in practice, very likely as a result of the pre-publishing approval 
process including discussion here, AFAIK no such post-publishing 
correcting revision has ever been necessary.  But that's not to say it 
won't /ever/ be necessary, so having the ability is certainly a good 
thing. =:^)


Either that or start out with a pre-publishing version of 0.1 and bump 
that, changing it to 1 on initial publish.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  parent reply	other threads:[~2015-03-27  2:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:56 [gentoo-dev] Review: Apache AddHandler news item Sebastian Pipping
2015-03-26 17:02 ` Michael Orlitzky
2015-03-26 18:15   ` Sebastian Pipping
2015-03-26 19:50     ` Marc Schiffbauer
2015-03-27  0:06       ` Sebastian Pipping
2015-03-30  0:03       ` Sebastian Pipping
2015-04-05 23:29         ` Sebastian Pipping
2015-04-06  4:53           ` [gentoo-dev] " Duncan
2015-04-06 12:56             ` Sebastian Pipping
2015-04-07  7:14               ` Duncan
2015-03-27  2:33     ` Duncan [this message]
2015-03-28 17:24       ` Sebastian Pipping

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$330d9$abb55956$eb57e62d$59b09efa@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox