On Mon, Mar 31, 2008 at 10:00:05AM -0700, Nicholas Clark wrote:
> Change 33614 by [EMAIL PROTECTED] on 2008/03/31 16:59:07
>
>
> Affected files ...
Ooh. That's not right. It should say:
Integrate:
[ 33239]
in unpack, () groups in scalar context were still returning a list,
resulting in garbage on the stack, which could manifest as a SEGV
(Bug 50256)
[ 33296]
Subject: [PATCH] Unused var in perlio.c (revised)
From: "Jerry D. Hedden" <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 10:00:18 -0500
Message-ID: <[EMAIL PROTECTED]>
[ 33301]
Subject: [PATCH] PERL_MAGIC_uvar_elem should be 'u' in dump.c
From: "Vincent Pit" <[EMAIL PROTECTED]>
Date: Wed, 13 Feb 2008 11:10:11 +0100 (CET)
Message-ID: <[EMAIL PROTECTED]>
[ 33334]
Enable caching of strxfrm() results also for readonly SVs as
returned e.g. by "keys %hash". This speeds up sorting of lots
of hash keys significantly. See also:
Subject: Slowdown of "sort keys %hash" under "use locale"
From: Marcus Holland-Moritz <[EMAIL PROTECTED]>
Date: Fri, 15 Feb 2008 17:00:15 +0100
Message-ID: <[EMAIL PROTECTED]>
[ 33388]
Do the memory debug header fixup earlier to avoid valgrind screaming
under -Dm. Also, temporarily disable memory logging during thread
memory freeing, as otherwise we try to log using memory we already
freed.
[ 33407]
Subject: [PATCH] for -M:Foo, extended and revised
From: "Robin Barker" <[EMAIL PROTECTED]>
Date: Wed, 27 Feb 2008 19:19:54 -0000
Message-ID: <[EMAIL PROTECTED]>
[ 33408]
Subject: Re: interrupting system() with signal depends on signal
handler
From: Steffen Ullrich <[EMAIL PROTECTED]>
Date: Tue, 26 Feb 2008 19:43:00 +0100
Message-ID: <[EMAIL PROTECTED]>
[ 33495]
Subject: [perl #51636] segmentation fault with array ties
From: [EMAIL PROTECTED] (via RT) <[EMAIL PROTECTED]>
Date: Wed, 12 Mar 2008 02:59:45 -0700
Message-ID: <[EMAIL PROTECTED]>
[ 33595]
Subject: [PATCH] do not use SVTYPEMASK to prevent cleaning of PL_fdpid
and PL_strtab
From: Gerard Goossen <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 26 Mar 2008 14:07:13 +0100
[ 33596]
Fix compiler warning about comparison of pointer types.
It now does.
It always did.
We thank Big Brother for raising the chocolate ration to 20g.
Nicholas Clark