Re: How to patch..
Eric,
you give a big amount of informations and a clear view to me about lots
of thinks i did not know.
Now I'm sure I have to study...a lot... :)
Also the link are very good!
..now I go to open a new topic on the list .. :)
Thanks again
Lorenzo
* Eric Gaumer <gaumerel@ecs.fullerton.edu> [031004, 09:25]:
>
> Uncompress these first.
>
> Apply the large patch first (mm) because chances are that the rtc-patch
> will fail here. If the rtc patch isn't against 2.6.8.1-mm4 then you may
> see hunks that fail. You'll need to fix these failures by hand.
>
> If you are not familiar with C code and/or kernel code, then this may be
> difficult for you to fix. It may be easier to have two source trees.
> Apply the mm patch to one and the rtc patch to the other. Then you can
> create your own patch that has mm and rtc merged together. This gives
> you a little flexibility as what the patches were applied to. Bitkeeper
> is good for this because you can clone trees easily, using hardlinks
> (see below).
>
> >
> > Or should I use a dfferent way?
> >
> > If I forget what patches I have installed how can can I see the list of
> > installed paches? :)
>
> Yes and no... Just using patch and diff you wont be able to see without
> keeping a directory of patches you applied to the tree.
>
> A utility called "Quilt" exists that allows you to push and pop patches.
> With this you can see what patches have been applied. Quilt is available
> via apt-get. This may sound really cool but be warned... Quilt is not
> something I would consider "for newbies". You should have a firm
> understanding of kernel patching first.
>
> http://packages.debian.org/unstable/devel/quilt
>
> There is also another utility called ketchup that may be of some help to
> you. This is an easy way to keep your tree up to date. It also supports
> the mm tree as well as a few others.
>
> http://kerneltrap.org/node/view/2976
>
> You could also check out Bitkeeper. It's free of charge (providing you
> keep your source open) and it makes merging changes easier. It's also
> GUI driven. Here is an article on kernel source control that makes for a
> decent primer.
>
> http://linuxjournal.com/article.php?sid=6183
>
> >
> >
> > Thanks and sorry for the log list of questions...I'm a Newb...
> > Lorenzo
>
>
> --
> Eric Gaumer <gaumerel@ecs.fullerton.edu>
> --
> Eric Gaumer <gaumerel@ecs.fullerton.edu>
Reply to: