Update of /cvs/scoop/scoop In directory lithium.sabren.com:/tmp/cvs-serv26254 Modified Files: README.contrib Log Message: Documentation updates. Bugs 98, 114, 144, 148, 149, 150, 151, 155. -janra Index: README.contrib =================================================================== RCS file: /cvs/scoop/scoop/README.contrib,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** README.contrib 28 Mar 2004 22:14:22 -0000 1.1 --- README.contrib 27 Feb 2005 13:28:36 -0000 1.2 *************** *** 101,105 **** command for this: ! $ cvs diff -c [files] > patch.diff The 'cvs diff' part runs the cvs program and tells it to compare the files on --- 101,105 ---- command for this: ! $ cvs diff -u [files] > patch.diff The 'cvs diff' part runs the cvs program and tells it to compare the files on *************** *** 107,112 **** differences between the two. ! The '-c' option makes a context diff instead of a unified diff. Be sure to use ! this, otherwise it is much more difficult for developers to review your patch. A list of files is optional. If not given, CVS will go through each directory --- 107,112 ---- differences between the two. ! The '-u' option makes a unified diff. Be sure to use this, otherwise it is much ! more difficult for developers to review your patch. A list of files is optional. If not given, CVS will go through each directory *************** *** 118,130 **** keep the .diff extension. - If you'd like, you can also compress your patch, with gzip or bzip2, though it - is optional. It makes no difference to the developers. - - Once you have your patch ready, you may want to put it up for comments. If so, - send it to the scoop-dev mailing list, with an explanation of what it does and - a request for comments. Do not put your patch in-line with the rest of the - message; you must attach it. If you do not, then line wrapping will most likely - break the patch. - When you think your patch is ready to be reviewed, attach it to your bug entry in the Scoop Bug Muncher and set the review? flag on the attachment. The --- 118,121 ---- *************** *** 137,141 **** after a week or so, you could try sending another email to see what its status is. There are several factors that could contribute to your patch not being ! reviewed right away, but a patch is never flat-out ignored. It's possible that your patch will be rejected, but don't be discouraged by --- 128,132 ---- after a week or so, you could try sending another email to see what its status is. There are several factors that could contribute to your patch not being ! reviewed right away, but a patch is never deliberately ignored. It's possible that your patch will be rejected, but don't be discouraged by