Procedure to make a patch

Oliveiros Cristina oliveiros.cristina at gmail.com
Mon Apr 21 23:49:04 UTC 2008


Hello, Pete.
Thank you for your prompt reply.

I guess I understand your explanation.
For ex, the first line of the patch is as follows :
diff -uNrp kernel-2.6.24.orig/linux-2.6.24.i686/include/linux/tipc_config.h
k
ernel-2.6.24.new/linux-2.6.24.i686/include/linux/tipc_config.h

and, yes, there are an extra slash here. p2 would be needed

The full diff command I've used was

diff -uNrp kernel-2.6.x.orig kernel-2.6.x.new >
../SOURCES/linux-2.6-my-new-patch.patch


But I guess I should have rather used

diff -uNrp kernel-2.6.x.orig/linux-2.6.24.i686
kernel-2.6.x.new/linux-2.6.24-i686 >
../SOURCES/linux-2.6-my-new-patch.patch



Do you agree with me?

I will try this to see what happens.

Thanks a million for your tip, Pete

Best,
Oliveiros

2008/4/22, Pete Zaitcev <zaitcev at redhat.com>:
>
> On Mon, 21 Apr 2008 23:30:07 +0100, "Oliveiros Cristina" <
> oliveiros.cristina at gmail.com> wrote:
>
> > diff -uNrp
>
> What were the other arguments?
>
>
> > The procedure I've used is essentially what is described here
> > http://fedoraproject.org/wiki/Docs/CustomKernel
> >
> > But, when the build process reaches my patch it stops and asks me "File
> to
> > patch:"
>
>
> Looks like you need to make sure patch -p1 can apply it.
> Look at the pathnames inside the resultng patch and make sure
> the number of slashes is the same as in other patches.
>
>
> -- Pete
>



-- 
"An equation for me has no meaning, unless it represents a thought of God."
- Srinivasa Ramanujan Iyengar



More information about the Fedora-kernel-list mailing list