It might be prudent to test against Apache 2.2.4, which was released two
days ago. I'll try to do this over the weekend and submit the results.
Jim Gallacher wrote:
We don't seem to be getting any more feedback on 3.3.0b (+1's across the
board), so how does everyone feel about rolling out
I just ported the patch to 2.2.4.
These are exactly the modification that are included in the version
running for more than a year in several major governmental sites in
Belgium (including the biggest one to fill in taxes) - it is thus stable
(at least the changes were stable in 2.0.54 ;-) .
On Thu, Jan 11, 2007 at 10:11:18PM -0800, Sander Temme wrote:
On Jan 11, 2007, at 1:40 PM, Ruediger Pluem wrote:
A week sounds good to me. I guess some of them are my fault as I only
set them to resolved fixed and never visited them again as I thought
that they reached their final state.
In latest version of OpenSSL libraries distributed by Shining Light
Productions, the names changed:
ssleay32.lib = ssleay32MT.lib (or ssleay32MTd.lib with debug info)
libeay32.lib = libeay32MT.lib (or libeay32MTd.lib with debug info)
Should we use these names in the project ?
Do you want
William A. Rowe, Jr. wrote:
Issac Goldstand wrote:
I'd agree if mod_ssl is disabled by default, but if it is, why are they
downloading the mod_ssl-enabled installer?
You miss the point, it's illegal in some jurisdictions to possess/use
such cryptography. That installer will remain as a
On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
What is the difference between a RESOLVED bug and a CLOSED
one? Is
it not possible to re-open/add comments to CLOSED reports or
something?
It's always seemed like a meaningless distinction to me, going through
marking stuff CLOSED seems like a
Joe Orton wrote:
On Thu, Jan 11, 2007 at 10:11:18PM -0800, Sander Temme wrote:
Yes, Closed should be the final resting place for bug reports, for
good or for bad.
What is the difference between a RESOLVED bug and a CLOSED one? Is
it not possible to re-open/add comments to CLOSED
On Jan 12, 2007, at 1:04 PM, Roy T. Fielding wrote:
On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
What is the difference between a RESOLVED bug and a CLOSED
one? Is
it not possible to re-open/add comments to CLOSED reports or
something?
It's always seemed like a meaningless distinction to
On 01/12/2007 11:14 PM, Sander Temme wrote:
On Jan 12, 2007, at 1:04 PM, Roy T. Fielding wrote:
On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
What is the difference between a RESOLVED bug and a CLOSED one? Is
it not possible to re-open/add comments to CLOSED reports or something?
lör 2007-01-13 klockan 01:06 +0100 skrev Ruediger Pluem:
This could be modified to:
1. Fix on trunk = Change state in Resolved, fixed and add a comment with
revision
of fix.
2. Proposed for backport = Leave state in Resolved, fixed and add a
comment with
revision of backport
I'm back to tinkering with mod_log_dbd again and I got to thinking about
timestamps. The current logging behavior writes the output of apr_time_now() to
the log, which naturally gives the time on the httpd server. But, the database
server also has its own timestamp functionality. Is there any
11 matches
Mail list logo
