Hi Nicholas Clark 
                     That is fine.   Now  I am clear about your problem.
Thanks for your explanation. 
Ok, Well , Mean time I applied all my Perl-5.8.4  changes to my
Perl-5.9.1 sources. 
Is it possible to apply  that  patch  to Perl-5.9.x  development branch.

 
If this is possible, I will send  my Perl-5.9.1-NetWare.patch  immly as
Perl-5.9.2  is in the  smoke as per Rafael Garcia-Suarez  mail. 
 
Thanks  for your comments on  my previous mail attached 
Perl-5.8.4-NetWare patches. 
I will incorporate all of your comments in the next patch. 
 
Have a nice day. 
 
Regards 
K.Murugan


>>>Nicholas Clark <[EMAIL PROTECTED]> 03/31/05 8:44 am >>>
On Wed, Mar 30, 2005 at 11:47:12PM -0700, Murugan K wrote:
>Hi 
>      Now I am able to  apply & test my patches successfully.  Thanks.
>
>But I have one more problem.  My Perl-5.8.4 attached patch file is not
>getting delivered to the [email protected] as my  patch file size
>is 430 KB (440,348 bytes).  I am getting  the  MAILER-DAEMON  failue
>message which is mentioned below.
>  Is ther any other way to split it into two patches and send it
>across.  But anyway ,  I want to  send as a  whole patch as we are
>sending  significant NetWare changes.

Don't send patches for 5.8.4

(This is what Dave was saying in the previous message)

Changes to 5.8.x are made by integrating them across from the
development
track.

The principle exception is for code no longer in the development branch,
such
as 5.005 threads.

I'm not going to apply bulk patches to 5.8.7-to be - instead I will wait
until
we verify that the code in the development branch is stable (in that it
doesn't break the build on any platforms we have access to or cause any
reported problems), and *then* it will be integrated to 5.8.x, the
maintenance
branch. I do this to try to keep the maintenance branch as stable as
possible.

In particular, I don't want to apply what are in your own words
significant
changes in one hit to stable, as it is almost certainly destabilising.

I realise that this may make your job harder, but you only have to deal
with
one platform. However, not doing this makes my job impossible, because
I'm
walking a tightrope of trying to keep every platform still working.
(job, because I'm doing this on a volunteer basis, as are the other core
perl developers)

Nicholas Clark

Reply via email to