From: Rich Freeman <rich0@gentoo.org>
To: k_f@gentoo.org
Cc: Sebastian Pipping <sping@gentoo.org>,
gentoo-dev <gentoo-dev@lists.gentoo.org>,
"pr@gentoo.org" <pr@gentoo.org>
Subject: [gentoo-dev] Re: News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Mon, 4 Jan 2016 07:11:10 -0500 [thread overview]
Message-ID: <CAGfcS_ncj-f9zoZ5Qf1tEZuGa9dYR8YMumJJdjPDJF9+jjrXkQ@mail.gmail.com> (raw)
In-Reply-To: <568A3039.7070106@gentoo.org>
On Mon, Jan 4, 2016 at 3:41 AM, Kristian Fiskerstrand <k_f@gentoo.org> wrote:
>
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>>
>>
>> Better late then never. Posting 72 hours from now the earliest as
>> advised by GLEP 42. Feedback welcome as usual.
>
> Do you have any timeline in place for the change happening in tree (in
> particular for stable users).
++
In particular we should avoid both of these scenarios:
1. Stable users make a change now which breaks their existing config
(because the change isn't deployed to stable yet).
2. Stable users get the news item today, and the change six months
later after they've forgotten about it.
I'm not sure whether either applies in this case.
--
Rich
next prev parent reply other threads:[~2016-01-04 12:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 0:26 [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP" Sebastian Pipping
2016-01-04 5:11 ` Jeroen Roovers
2016-01-04 16:53 ` Michael Orlitzky
2016-01-04 8:41 ` [gentoo-dev] " Kristian Fiskerstrand
2016-01-04 12:11 ` Rich Freeman [this message]
2016-01-04 13:30 ` Kristian Fiskerstrand
2016-01-04 14:20 ` Kristian Fiskerstrand
2016-01-04 14:51 ` Rich Freeman
2016-01-04 14:45 ` Peter Stuge
2016-01-04 15:08 ` Brian Evans
2016-01-04 10:45 ` [gentoo-dev] " Lars Wendler
2016-01-04 13:40 ` Michał Górny
2016-01-04 15:20 ` Michael Orlitzky
2016-01-04 15:42 ` Peter Stuge
2016-01-04 15:53 ` Michael Orlitzky
2016-01-04 16:11 ` Peter Stuge
2016-01-04 16:43 ` Michael Orlitzky
2016-01-04 17:21 ` Brian Evans
2016-01-04 17:49 ` Rich Freeman
2016-01-04 19:27 ` Michael Orlitzky
2016-01-05 19:35 ` Michael Orlitzky
2016-01-06 19:36 ` Sebastian Pipping
2016-01-06 19:53 ` Michael Orlitzky
2016-01-08 0:52 ` Marc Schiffbauer
2016-01-09 17:39 ` Michael Orlitzky
2016-01-06 19:39 ` Sebastian Pipping
2016-01-04 15:11 ` Hanno Böck
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=CAGfcS_ncj-f9zoZ5Qf1tEZuGa9dYR8YMumJJdjPDJF9+jjrXkQ@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=k_f@gentoo.org \
--cc=pr@gentoo.org \
--cc=sping@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