|
From: <hzu...@ra...> - 2003-12-08 12:10:52
|
On 12/05/2003 12:47:48 AM Martin Glazer wrote: >On December 4, 2003 06:20 am, Bruce Smith wrote: > ><snip> > >> > It would be great if you can send us a "diff" next time, we prefer >this. >> > You find it in the generated docu how to do this (I don't think >it's on >> > the website yet). > >Next time, if I can figure out this diff and patch thing I will. The >doc I >found only talks about single file patches though. Really ? It's easy, just add the parameter -r (or -R ?) and specify directories instead of files. >> Look at the man page for "patch", it gives a good example for a >> recursive unified diff. >> > >I know how to do patch files for single files, but not for complete >directories. Do I need to keep 2 copies of my build directories - one >with my I do it usually with 2 directories, i.e. scripts & scripts.orig >new files and the other with the standard DL cvs? or can I do a cvs diff >somehow? Never used cvs diff.... >Excuse my ignorance in these matters, but I'm not used to submitting >patches. > >If I try using 2 build directories, this command (from the man page) >appears >to work... >diff -Naur --exclude=tmp build build.new/ > patchfile.diff That should work just fine. >How have other contributors setup their build/development systems? Inside the lfssystem I usally use the path /data/build , but you can use whatever you want. Heiko |