Send email to: modperl-unsubscr...@perl.apache.org

On 6 August 2014 08:20, Tabassum Fathima <tabassum.fath...@mphasis.com> wrote:
> Hi all,
>
> Could you please tell me how will I un-subscribe from these group?
>
>
>
> -----Original Message-----
> From: olli hauer [mailto:oha...@gmx.de]
> Sent: Sunday, August 03, 2014 8:55 PM
> To: Kurt Jaeger; Patrick Powell
> Cc: po...@freebsd.org; modperl@perl.apache.org
> Subject: Re: Apache 24 + mod_perl
>
> On 2014-08-01 23:34, Kurt Jaeger wrote:
>> Hi!
>>
>>> Question:  when will mod_perl be available for Apache 24?
>>
>> There's a PR where people are discussing this:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471
>>
>> This PR needs more testers etc.
>>
>
> I've updated the PR with a patch against the latest mod_perl trunk revision 
> (r1602105).
>
> The patch against the port can be grabbed from here or from our bugzilla 
> http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff
>
> Please test *at own risk*, and report issues to upstream and here so we can 
> integrate fresh upstream fixes and update the port.
>
> The first proposed patch will allows the port to build but I have to many 
> concerns for integrating this simple fix into the tree.
> I don't believe the first patch on the PR will work right else it would take 
> the upstream dev. work and time for mod_perl2 at absurd-um ...
>
>
> --
> regards,
> olli
> Information transmitted by this e-mail is proprietary to Mphasis, its 
> associated companies and/ or its customers and is intended
> for use only by the individual or entity to which it is addressed, and may 
> contain information that is privileged, confidential or
> exempt from disclosure under applicable law. If you are not the intended 
> recipient or it appears that this mail has been forwarded
> to you without proper authority, you are notified that any use or 
> dissemination of this information in any manner is strictly
> prohibited. In such cases, please notify us immediately at 
> mailmas...@mphasis.com and delete this mail from your records.
>

Reply via email to