[development] create patch form

[Rob Barreca]

> Unless of course, you all are about to point out how I could be doing 
> this better now, :) 
For Windows, TortoiseCVS is a great tool and the latest dev version lets 
you do diff -up without going to the command line. And I just throw the 
patches in Notepad++ and convert to Unix line endings. In the near 
future, TortoiseCVS should have a bit better patch support and maintain 
line endings well so it will be even easier.

It should be pretty easy to get most Windows users (which might be most 
users who have trouble patching in the first place) up to speed using 
TortoiseCVS and Notepad++, both which don't require going to the command 
line. Maybe I should add a bit more to that TortoiseCVS handbook page...

Rob Roy Barreca
Founder and COO
Electronic Insight Corporation
http://www.electronicinsight.com
rob at electronicinsight.com



Sam Tresler wrote:
>> I agree with killes. If a user can't diff... I'd expect patches against
>> the wrong version of a module and/or patches that provide poor or
>> incorrect solutions to problems.
>
> This provides a 'standard' to diff that even new users who can diff 
> might not know.  Windows line breaks, and -p to make things cleaner to 
> read... Heck, sometimes people just forget those and the maintainer 
> gets to re-roll the patch anyway.  My windows box I need Cygwin to do 
> a proper command line diff and I need to run it through dos2unix 
> first... this would actually make it easier for some developers.
>
> Unless of course, you all are about to point out how I could be doing 
> this better now, :)
>
> To me the main value in this is a diff validation of sorts.
>
> - Check versions so the module being uploaded _is_ diffed against the 
> proper CVS version.
> - Auto-remove windows line breaks
> - Automatically use -p
> - Automaticaly determine the right place in the directory structure to 
> take the diff from (Would allow multiple file uploads I presume)
>
>