> Patches should be submitted to the developers mailing list.
> Always use diff -u to generate patches, make sure you are patching the latest cvs (the HEAD).
> + (Note: If you use WinCVS, move to [Admin] -> [Command Line] Menu and type "cvs diff -u" at [Enter a cvs line command] input field ([Commandline Settings] Tab), while selecting the target directories or files, in order to create unified diffs.)
> Make your patch from the jakarta-james directory and make sure it conforms
> - to the code standards, otherwise it may be ignored. Its is OK to make a single patch covering several
> + to the code standards, otherwise it may be ignored. It is OK to make a single patch covering several
> files, but please only one issue at a time.
> Prefix the mail subject with [PATCH]
> Briefly outline the reason for your patch,
> @@ -48,7 +49,7 @@
> your submission conforms to the code standards. Provide a Brief outline of
> your intentions, as above, so that your code can be reviewed easily, and a
> note of any relevant bug numbers.
> - New files must contain a refrence to the Apache licence, copy the header from an existing file.
> + New files must contain a reference to the Apache license, copy the header from an existing file.
> It also helps if you send your files in an archive (tar, zip) which preserves directories, make it from the jakarta-james directory so we can un-tar your files into the right place.
>