Randy Kobes wrote:
Just so as to not give the impression that this would be a
lonelier job than the Maytag repairman ...:) There's a few
(small) things for Win32 that I've gathered over the last little
while - a couple bugs in the build process, and some things to
get rid of some warnings - that
Philippe M. Chiasson wrote:
On Wed, 2003-01-22 at 11:39, Stas Bekman wrote:
Philippe M. Chiasson wrote:
[...]
Doug will still handle the release management. What we need help with, is
maintaining the STATUS file and verifying and following up on submitted
patches so not to discourage contribu
Nick Tonkin wrote:
Might I suggest the following messages instead:
Good input, Nick
apr/threadmutex..skipped
test skipped: threads not installed or 'APR::ThreadMutex' not found
Now it'll say:
apr/threadmutex1..0 # skipped: Apache/APR was built without threads support
er
On Thu, 2003-01-16 at 08:03, Stas Bekman wrote:
> Dmitri Tikhonov wrote:
> > Hi everyone,
> >
> > I just upgraded to 1.99_08, and it lets me do all my old
> > configurations. Except for one.
> >
> > When I try to do something like
> >
> >
> > push @Listen, 80;
> >
> > # or this:
> >
On 22 Jan 2003, Philippe M. Chiasson wrote:
> On Wed, 2003-01-22 at 09:08, Stas Bekman wrote:
[ .. ]
> > Doug will still handle the release management. What we need
> > help with, is maintaining the STATUS file and verifying and
> > following up on submitted patches so not to discourage
> > contri
On Wed, 2003-01-22 at 11:39, Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> [...]
> >>Doug will still handle the release management. What we need help with, is
> >>maintaining the STATUS file and verifying and following up on submitted
> >>patches so not to discourage contributions. (again tal
Philippe M. Chiasson wrote:
[...]
Doug will still handle the release management. What we need help with, is
maintaining the STATUS file and verifying and following up on submitted
patches so not to discourage contributions. (again talking mod_perl 1.0 here).
Isn't Geoffery taking care of this a
On Wed, 22 Jan 2003, Stas Bekman wrote:
> Nick Tonkin wrote:
>
> > But still:
> >
> > directive/setupenv...ok
> > error/push_handlers..# Failed test 1 in error/push_handlers.t at
> > line 14
> > error/push_handlers..FAILED tes
On Wed, 2003-01-22 at 09:08, Stas Bekman wrote:
> Stas Bekman wrote:
> > Once in a while we get mod_perl 1.0 patches posted from the kind folks.
> > I'm trying to cope with 2.0 and I'm not very familiar with 1.0 guts, so
> > I commit only things that I know about. Doug is too busy at work, so he
Stas Bekman wrote:
Once in a while we get mod_perl 1.0 patches posted from the kind folks.
I'm trying to cope with 2.0 and I'm not very familiar with 1.0 guts, so
I commit only things that I know about. Doug is too busy at work, so he
is not here to do that. Therefore we need someone to take ca
Once in a while we get mod_perl 1.0 patches posted from the kind folks. I'm
trying to cope with 2.0 and I'm not very familiar with 1.0 guts, so I commit
only things that I know about. Doug is too busy at work, so he is not here to
do that. Therefore we need someone to take care of those infreque
Geoffrey Young wrote:
I gave this some more thought and I think that this approach would be
too ineffective. I think if we ever need only *one* filter_init
function
per package (filter), we could have a special name for it, similar to
INIT, BEGIN, etc. e.g.:
sub FILTER_INIT {
#
}
T
Nick Tonkin wrote:
But still:
directive/setupenv...ok
error/push_handlers..# Failed test 1 in error/push_handlers.t at
line 14
error/push_handlers..FAILED test 1
Failed 1/1 tests, 0.0
On Tue, 21 Jan 2003, Daryl Lee wrote:
> Problem solved. The root cause was staring me in my face and I missed it.
> Under mod_perl, the connection attempt was through /tmp/mysql.sock, but
> (for reasons that totally escape me) all other communication with mysql is
> through /var/lib/mysql/mysql.s
On Tue, 21 Jan 2003, Stas Bekman wrote:
> Nick Tonkin wrote:
> > On Mon, 20 Jan 2003, Stas Bekman wrote:
> >
> >
> >>Nick Tonkin wrote:
> >>
> >apr/threadmutex..FAILED tests 1-3
> > Failed 3/3 tests, 0.00% okay
> [...]
>
> Thanks Nick an
I gave this some more thought and I think that this approach would be
too ineffective. I think if we ever need only *one* filter_init function
per package (filter), we could have a special name for it, similar to
INIT, BEGIN, etc. e.g.:
sub FILTER_INIT {
#
}
This will make the lookup
Problem solved. The root cause was staring me in my face and I missed it.
Under mod_perl, the connection attempt was through /tmp/mysql.sock, but
(for reasons that totally escape me) all other communication with mysql is
through /var/lib/mysql/mysql.sock. A symlink at /tmp pointing to the
correct
17 matches
Mail list logo
