> this patch if you like. I couldn't find any "patch submission > guidelines" on the coder-com web site, except this: > > # A patch must be submitted with a separate description section that > # include standard header fields, and the actual patch should be in > # "diff-rc3" format. > > I haven't really patched anything before, so I don't know what > "standard header fields" would be, or how to properly include them in > a diff file. Also, the man page for my version of diff doesn't say > anything about "rc3" so... But, the entire thing is only 3 lines, > really it takes just as long to simply type in the changes manually as > it does to apply the patch. ;)
ergh. We should probably update that to explain what we mean. FTR, guidelines are: 1) Patches MUST include appropriate ChangeLog entries. 2) Patch submissions MUST include an explanation of the patch appropriate for including in commit logs. 3) Patches SHOULD be submitted in unified format (diff -u). Context format is acceptable but strongly discouraged. No other format will be accepted. 4) Since all patches must include ChangeLog entries, they must be generated with the equivalent of the -r (recursive) flag to diff. 5) Patches SHOULD be submitted via the SourceForge trackers. (The patch you submitted will probably be applied despite violation of 1 above, assuming it doesn't get lost in my mailbox--which is the reason for 5 ;) -- Kevin L. Mitchell <[EMAIL PROTECTED]>
