How to submit patches to the project

back
Introduction

The preferred method of collaboration for esablished members is CVS. Non-members may still participate by sending patches.

All this was experimented on cygwin.

Produce a patch
If your work directory is ww_current, to make a patch based on build 15 do: 
lotzmana@safe$ cd ~/work
lotzmana@safe$ unzip ~/temp/ww_b15.zip
lotzmana@safe$ ls -F
ww_b15/  ww_current/
lotzmana@safe$ diff -rbu ww_b15 ww_current | gzip -9 > feature_b15.patch.gz
(-r recursive in subdirectories; -b ignore space changes; -u output unified context)
Patch it

On the receiving side, if my work on the new build 16 is planned to start in ww_current. 

lotzmana@safe$ cd ~/work
lotzmana@safe$ ls -l
ww_current/
lotzmana@safe$ cd ww_current
lotzmana@safe$ gzip -d -c feature_b15.patch.gz | patch -p0 -u -l
(-d decompress; -c to stdout; -p0 skip no dir in filenames; -u use unified context; -l loosely match spaces)

I may use -p1, when ww_b15 was not the working directory for diff. Patch strictly requires unix EOL format for features_b15, if patch fails I will use dos2unix, or the WW :-), to convert to unix EOL format.

[-petar]

last updated: nov-2003 | first version: nov-2003 | back