Joachim and Nick,

Thanks for the advice. I was just think about how to minimize the impact for
production boxes based on previous release (4.0, 4.1...).

Kevin 

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> On Behalf Of Joachim Schipper
> Sent: Monday, August 27, 2007 4:21 AM
> To: [email protected]
> Subject: Re: Backport drivers from 4.1 to 4.0
> 
> On Mon, Aug 27, 2007 at 02:42:34AM +0800, Kevin Cheng wrote:
> > Hi Darrin,
> > 
> > Thanks for reply.
> > 
> > The reason is that we have bunch of files integrated with 
> 4.0 and it would
> > take us months to upgrade to 4.2 again. we just finished 
> from 3.3 to 4.0 of
> > upgrade few months ago, plus months of test to stabilize 
> our 4.0 based
> > applications.
> > 
> > Should we just isolate one by one manually as safety 
> approach?  Any CVS that
> > we can trace for what files been changed for specific drivers? E.g.,
> > 4.0->4.1.
> 
> I'd like to point out that 4.0->4.2 will be *a lot* easier than
> 3.3->4.0.
> 
> You can, of course, use any of the AnonCVS mirrors, linked 
> from the home
> page. But that is still the wrong approach.
> 
>               Joachim

Reply via email to