[let's split this from the VOTE thread and have a dedicated thread]
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>>Philippe M. Chiasson wrote:
>>
>>
>>>Stas Bekman wrote:
>>>
>>>
Philippe M. Chiasson wrote:
>[...]
>>>
>>>The problem I see is the lookup. How do you find all m
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>> Stas Bekman wrote:
>>
>>> Philippe M. Chiasson wrote:
>>>
[...]
>>
>> The problem I see is the lookup. How do you find all modperl_mgv * for
>> "Some::NameSpace"? AFAIK, they are located in modperl_handler_t's and
>> these
>> are buried dee
Markus Wichitill wrote:
Stas Bekman wrote:
Seeing how painful was the last branch's merge, I was wondering if
there is an automatic way to keep the branch in sync with the trunk.
Unfortunately not, that would require merge tracking, which is one of
Subversion's medium-term goals.
http://subver
Stas Bekman wrote:
Seeing how painful was the last branch's merge, I was wondering if there
is an automatic way to keep the branch in sync with the trunk.
Unfortunately not, that would require merge tracking, which is one of
Subversion's medium-term goals.
http://subversion.tigris.org/roadmap.h
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
My plan was to polish things this week (add registryprefork and stuff),
get the 2.0.0-RC on friday and release 2.0.0 on monday if everything is
cool.
I'd probably add slightly more time between the RC and the release,
espec
Seeing how painful was the last branch's merge, I was wondering if there
is an automatic way to keep the branch in sync with the trunk. So if I have:
https://svn.apache.org/repos/asf/perl/modperl/branches/clone-skip-unstable/
is there a way to automatically bring in all the changes in the trunk,
Jim Martinez wrote:
On May 9 Stas Bekman wrote:
So the next stage is probably to move:
svn move src/docs/general/testing/testing.pod \
src/projects/Apache-Test/user/perl/guide.pod
is that good? I suppose it'd be a good idea to split it in smaller docs?
I like it. Thanks.
The testing doc
Nick *** wrote:
>Thanks, committed.
>
>> I didn't use File::Copy, because it's not use(d) at the beginning of
Build.pm, so I thought it isn't loaded.
>
>It should be loaded. I've added the loading.
>
Thanks Stas. Meanwhile I've cooked another patch, but first...
This code in ModPerl::BuildOp
Philip M. Gollucci wrote:
[EMAIL PROTECTED] wrote:
Author: stas
Date: Wed May 11 08:14:51 2005
New Revision: 169644
URL: http://svn.apache.org/viewcvs?rev=169644&view=rev
Log:
make sure that the build picks up the include directories based on the
apxs queries and only search the httpd source if $se
[EMAIL PROTECTED] wrote:
Author: stas
Date: Wed May 11 08:14:51 2005
New Revision: 169644
URL: http://svn.apache.org/viewcvs?rev=169644&view=rev
Log:
make sure that the build picks up the include directories based on the
apxs queries and only search the httpd source if $self->{MP_AP_PREFIX}
was set
Stas Bekman wrote:
Stas Bekman wrote:
Hmm, for some reason I get t/api/module.t failing on perl's test
modules when buildiing with 2.0.49:
my $mmn_major = $cfg->{httpd_info}{MODULE_MAGIC_NUMBER_MAJOR};
my $mmn_minor = $cfg->{httpd_info}{MODULE_MAGIC_NUMBER_MINOR};
for (my $modp = $top
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>>> My plan was to polish things this week (add registryprefork and stuff),
>>> get the 2.0.0-RC on friday and release 2.0.0 on monday if everything is
>>> cool.
>>
>> I'd probably add slightly more time between the RC and the release,
>> especial
>Thanks, committed.
>
>> I didn't use File::Copy, because it's not use(d) at the beginning of
>> Build.pm, so I thought it isn't loaded.
>
>It should be loaded. I've added the loading.
>
Thanks Stas. Meanwhile I've cooked another patch, but first...
This code in ModPerl::BuildOptions bugs
13 matches
Mail list logo
