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: News item: Upgrading Apache from 2.2 to 2.4
Date: Thu, 14 Jan 2016 09:53:20 +0000 (UTC)	[thread overview]
Message-ID: <pan$7dde2$b41acaba$6a3b1898$49d9e73@cox.net> (raw)
In-Reply-To: CAKmKYaDSrvFYsN2hZL9ia5d1RY37heUdJhBGcTZyix980e8aNA@mail.gmail.com

Dirkjan Ochtman posted on Wed, 13 Jan 2016 18:13:41 +0100 as excerpted:

> Display-If-Installed: www-servers/apache

Can't that be made <www-servers/apache-2.4 ?  Why would people already on 
2.4 need a news item about something they've already taken care of?

Then ensure that the news item hits before the 2.4 stabilization, so it's 
known to be there and trigger when people update, so they get the news 
item either before they do the update or with the same run.

-- 
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:[~2016-01-14  9:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 17:13 [gentoo-dev] News item: Upgrading Apache from 2.2 to 2.4 Dirkjan Ochtman
2016-01-14  0:34 ` Daniel Campbell
2016-01-14  9:53 ` Duncan [this message]
2016-01-14 21:41   ` [gentoo-dev] " Dirkjan Ochtman
2016-01-14 21:58     ` [gentoo-dev] " Marc Schiffbauer
2016-01-17 18:18 ` [gentoo-dev] " Dirkjan Ochtman
2016-01-18 13:15   ` Daniel Campbell
2016-01-18 14:32   ` Aaron W. Swenson
2016-01-20 12:16 ` Dirkjan Ochtman
2016-01-21 12:52   ` Lars Wendler
2016-01-21 18:29     ` Paul Varner
2016-01-22 14:04       ` Dirkjan Ochtman
2016-01-22 14:20         ` Kristian Fiskerstrand
2016-01-27 14:17           ` Dirkjan Ochtman
2016-01-27 14:22             ` Kristian Fiskerstrand

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$7dde2$b41acaba$6a3b1898$49d9e73@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