You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2001/01/21 02:10:25 UTC
Core dumps and 1.3.15 / 1.3.16-dev
As a summary, during the tagging of 1.3.15, CVS would dump core,
locally and remotely (from several different systems) right around
the src/os/win32 location. Something is weird there.
Anyway, while we sort this out, I've gone ahead and bumped us
to 1.3.16-dev, but we're still in code freeze. I figured this
was the safest course of action, instead of trying to continue
with the tagging after some "extended period".
So, once we track this down, I'll tag and roll 1.3.16. Because
of the ApacheCon planner's meeting, I'll be offline from about
noon eastern till late tomorrow (Sunday) night. So it's
*possible* that we won't get a t&r until Monday (assuming this
core dump problem is solved beforehand).
--
===========================================================================
Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/
"Casanova will have many weapons; To beat him you will
have to have more than forks and flatulence."
Re: Core dumps and 1.3.15 / 1.3.16-dev
Posted by Greg Stein <gs...@lyra.org>.
On Sat, Jan 20, 2001 at 08:10:25PM -0500, Jim Jagielski wrote:
> As a summary, during the tagging of 1.3.15, CVS would dump core,
> locally and remotely (from several different systems) right around
> the src/os/win32 location. Something is weird there.
>
> Anyway, while we sort this out, I've gone ahead and bumped us
> to 1.3.16-dev, but we're still in code freeze. I figured this
> was the safest course of action, instead of trying to continue
> with the tagging after some "extended period".
>
> So, once we track this down, I'll tag and roll 1.3.16. Because
> of the ApacheCon planner's meeting, I'll be offline from about
> noon eastern till late tomorrow (Sunday) night. So it's
> *possible* that we won't get a t&r until Monday (assuming this
> core dump problem is solved beforehand).
You can just go ahead and tag with 1.3.15. Your tag will reposition any
existing 1.3.15 tags. Since we haven't released a 1.3.15, there is no
possible tarball mismatch.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/