On Mon, Sep 29, 2008 at 02:50:58PM +0200, Moritz Lenz wrote:
> Michael G Schwern wrote:
> > Steve Hay wrote:
> >> Michael G Schwern wrote:
> >>> http://schwern.org/src/ExtUtils-MakeMaker-6.46.tar.gz
> >>>
> >> 
> >> Thanks, applied to blead as #34440. Three local changes remain in blead,
> >> not yet assimilated into the CPAN EU::MM distro.
> > 
> > Are they a secret?
> 
> They are in a public source code repository. I'm sure you know where to
> find them.

But I agree with Schwern, in that if it's possible to count that there 3, then
it's trivial to list the numbers.

The commit message is:

Change 34440 by [EMAIL PROTECTED] on 2008/09/29 09:14:25

        Upgrade to ExtUtils-MakeMaker-6.46
        
        Local changes 32905 and 32964 in MM_Unix.pm and 33259 in MM_Unix.t
        remain

Change 32905 by [EMAIL PROTECTED] on 2008/01/08 22:45:03

        Subject: [patch] [Win32] Make Perl build on Win32 when the path 
contains whitespace
        From: Max Maischein <[EMAIL PROTECTED]>
        Date: Mon, 07 Jan 2008 20:48:04 +0100
        Message-ID: <[EMAIL PROTECTED]>


Change 32964 by [EMAIL PROTECTED] on 2008/01/12 01:01:45

        Don't quote a whitespace-containing ABSPERL when the whitespace
        means it is a command with parameter(s).


http://public.activestate.com/cgi-bin/perlbrowse/p/32905
http://public.activestate.com/cgi-bin/perlbrowse/p/32964

but I have no idea what the third change is.

(And, no, it's not actually that easy to work out what the changes are.
You have to do a diff between files in trees that are in two different
layouts, identify what are actual changes, and then use blame annotation to
work out what caused those changes. Possibly digging down through more than
one level of blame annotation)


We ask that bug reports are sent with perlbug, and get grumpy when "vendor"s
don't send us anything back upstream. Schwern is our upstream for MakeMaker,
and requests that we use the RT queue to track things. Either both parties'
requests are reasonable and should be followed, or neither.

Nicholas Clark

Reply via email to