On 21/07/2014 04:40, olli hauer wrote:
On 2014-07-20 19:14, Graham Leggett wrote:
On 20 Jul 2014, at 18:03, dev wrote:
Has 2.4.10 been released or not ?
It has been released, but we need to wait for the mirrors to update
before formerly announcing the release.
Regards,
Graham
--
Looki
On 2014-07-20 19:14, Graham Leggett wrote:
> On 20 Jul 2014, at 18:03, dev wrote:
>
>> Has 2.4.10 been released or not ?
>
> It has been released, but we need to wait for the mirrors to update before
> formerly announcing the release.
>
> Regards,
> Graham
> --
>
Looking at the http://www.ap
On July 20, 2014 at 1:14 PM Graham Leggett wrote:
> On 20 Jul 2014, at 18:03, dev wrote:
>
> > Has 2.4.10 been released or not ?
>
> It has been released, but we need to wait for the mirrors to update
> before formerly announcing the release.
I see, I just accidentally landed on the moment of
On 20 Jul 2014, at 18:03, dev wrote:
> Has 2.4.10 been released or not ?
It has been released, but we need to wait for the mirrors to update before
formerly announcing the release.
Regards,
Graham
--
On Sun, Jul 20, 2014 at 1:03 PM, dev wrote:
>
>
> Has 2.4.10 been released or not ?
>
>
> 2.4.10 is in the middle of the release process. 2.4.10 was approved but
the announcement wasn't sent out while mirrors are being populated.
> 1) The front page https://httpd.apache.org/ says "Apache http
Has 2.4.10 been released or not ?
1) The front page https://httpd.apache.org/ says "Apache httpd 2.4.9
Released "
https://httpd.apache.org/
2) The announce page says "Apache HTTP Server 2.4.10 Released "
http://www.apache.org/dist/httpd/Announcement2.4.html
3) The http
Le 20/07/2014 15:45, Marion & Christophe JAILLET a écrit :
My may concern is to keep 2.4 and trunk as close as possible, but
should I also see what can be backported to 2.2 ?
s/may/main/
Hi
I have proposed for backport for 2.4. See STATUS.
http://svn.apache.org/r1611978
http://svn.apache.org/r1612068
should merge without any trouble and should not generate any conflict
with code only in trunk, should it be backported one day.
What I have submitted and not proposed for
I'd strongly encourage backporting, if accepted on 2.x branch.
The APn code exists to find guidance through web, email archives and forum
searches. Keeping these consistent between 2.4 and 2.next is crucial.
It also ensures further backports apply without a host of future conflicts.
Christ
Le 19/07/2014 22:44, William A. Rowe Jr. a écrit :
If it violates 80 col formatting style rule, absolutely do not shift
the APLOGNO macro to the first line.
Sure.
Moreover, when submitting patches, I'll take care to only propose things
that can be backported easily.
Changes relying on othe
10 matches
Mail list logo
