Re: [Ltib] How do kernel patches get into LTIB?

[Stuart Hughes]

Hi Henri,

If you check-out ltib using CVS (recommended), then all you need to do 
to update is to change into the base of your check-out (where the ltib 
script is) and then run:

cvs up -dP

if you just want to see if anything has been updated without actually 
changing your local working copy you can do:

cvs -nq up

Regards, Stuart

On 20/09/11 03:16, Henri Kjellberg wrote:
> After some poking around I realized that you can get the latest set of
> patches by getting a new checkout of LTIB from using CVS. Is there a
> way to do this without creating a new ltib folder?
>
> Kind Regards,
> Henri
>
> On Mon, Sep 19, 2011 at 4:44 PM, Henri Kjellberg
> <address@hidden>  wrote:
> > Hello all,
> >
> > I am quite new to developing on embedded Linux and attempting to
> > understand how LTIB functions. I am working with the Phytec LPC3250.
> > How do the patches that are developed in the lpclinux group get into
> > LTIB? Currently, if I run LTIB on my machine I can see in the
> > /rpm/SOURCES folder there are all the patches to the kernel up to
> > kernel-arm-2.6.34-lpc32xx-v108.patch, but if I look at the
> > ftp.lpclinux.com linux-2.6.34-lpc32xx.git summary I see there is a
> > v1.09 patch that was tagged on 2011-08-26. How do these patches get
> > into LTIB? Is there a way to update LTIB so that I have that latest
> > patch?
> >
> > Thanks,
> > Henri Kjellberg
> > Satellite Design Laboratory
> > University of Texas at Austin
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib