You don't really write patches... you write code in the current code
that's already there, and then you use diff to generate patches...

this is very easy if you are using cvs to keep track of your code...

cvs diff file.c (I like to use cvs diff -u but that's personal
preferance).

if you aren't using cvs then you have to keep a copy of the original
source and do this

diff -u file.c.orig file.c.modified

Ken

On Thu, 21 Nov 2002, Wilkinson,Alex wrote:

> Howdy crew,
>
> Can someone point me to a paper that explains the process of
> writing patches.
>
> Cheers
>
>  - aW
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to