Doesn't look it is generating. pgollucci do you know where the doc
build code is executed?
2012/3/19 Fred Moyer :
> The live documentation should rebuild automatically. If it doesn't show up in
> a few hours send another ping and I'll take a look.
>
>
> On Monday, March 19, 2012 at 9:24 AM, Tors
The live documentation should rebuild automatically. If it doesn't show up in a
few hours send another ping and I'll take a look.
On Monday, March 19, 2012 at 9:24 AM, Torsten Förtsch wrote:
> Hi,
>
> is there anything other than "svn ci" I have to do to get documentation
> changes to the
Hi,
is there anything other than "svn ci" I have to do to get documentation
changes to the web site? A few minutes ago I committed changed to document the
pool cleanup behavior in case a cleanup function dies:
Sendingapi/APR/Pool.pod
Sendingapi/Apache2/ServerUtil.pod
Trans
On Saturday, 17 March 2012 07:36:45 Fred Moyer wrote:
> Cool I'll roll the Apache::* rc's first and wait a few more days on 2.0.6
> rc3
Fred, I am done.
The pool cleanup exception stuff turned out to be a real bug.
As for the null pointer in dconf->sec_file, I couldn't figure out how it can
hap
On Monday, 19 March 2012 08:32:41 Vick Khera wrote:
> > After a bit odf thinking about it I tend to forbid pool cleanups (and
> > PerlCleanupHandlers) to die. If they do we can:
...
> > 2) stringify it and write it to STDERR
> >
> > 3) gather it in a special hash, e.g. @APR::Pool::cleanup_exceptio
On Mar 18, 2012, at 9:41 AM, Torsten Förtsch wrote:
> After a bit odf thinking about it I tend to forbid pool cleanups (and
> PerlCleanupHandlers) to die. If they do we can:
>
> 1) completely ignore the exception
>
> 2) stringify it and write it to STDERR
>
> 3) gather it in a special hash, e
