Pattrick Hueper wrote:
> Hi,
>
>>>
>>> That being said,
>>> cvs diff -u
>>> creates patches that the patch program does not like. It is better
>>> to have two snapshots of the source code and use diff -u or diff
>>> -urN to create the patch file.
>>
>>
>
> uups, didnt know that, i only tried my file with kompare, and that
> worked...
>
> whats the procedure to create a good patch file? If i create a new
> snapshot, update it and run diff -urN, it of course reports all the
> files generated by the compile, and it also reports differences in
> CVS/... files. Is there any way around that?
>
> Patty
Run make distclean before generating the patch. Also, pass -X dontdiff
(file attached) to tell diff to ignore CVS and other files that should
not be included in the path.
Jamey
*~
*.a
*.o
*.orig
*.rej
*.ver
*.bin
*_MODULES
*cscope*
cs.out
.*
*.aux
*.dvi
*.eps
*.log
*.pdf
*.css
*.gif
*.jpeg
*.html
*.ps
*.sgml
*.tex
docproc
53c8xx_d.h
CVS
System.map*
aicdb.h
aicasm
asm
autoconf.h
bbootsect
bbootsect.s
bootsect
bootsect.s
bsetup
bsetup.s
btfix.s
btfixupprep
build
bvmlinux
bvmlinux.out
bzImage
classlist.h
comp*.log
compile.h
config
config_data.h
conmakehash
consolemap_deftbl.c
defkeymap.c
devlist.h
dummy_sym.c
filelist
gen-devlist
gen-kdb_cmds.c
gentbl
kconfig.tk
ksym.c
ksym.h
lxdialog
make_times_h
map
map.out
mkdep
modversions.h
ppc_defs.h
promcon_tbl.c
setup
setup.s
sim710_d.h
sm_tbl*
split-include
tags
TAGS
times.h
tkparse
version.h
vmlinux
vmlinux.out
zImage
fore200e_pca_fw.c
fore200e_mkfirm
zImage
Received on Mon Mar 01 15:17:51 2004
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:41:46 EDT