Actually, use:
cvs diff -u
Thats the recommended patch format.
Erik
----- Original Message -----
From: "Jim White" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Monday, December 24, 2001 2:54 PM
Subject: Re: Ant contributor
> At 09:06 AM 12/24/2001 -0800, [EMAIL PROTECTED] wrote:
> >I have developed a fix for ant and would like to submit it. Of course I
> >don't have access to check in code.
> >
> >What is the best way to go about this? Do I post my code to the listserv
> >for people to vote on?
>
> Against an up-to-date CVS checkout, do a "cvs diff -c" on the files with
> your fix. Post that to this list. Make sure you update the test suite to
> demonstrate and verify-as-fixed the bug and include that with your patch
diff.
>
> I did that with a bug I fixed last week and it was checked into CVS within
> an hour (of course turnaround that quick shouldn't be expected as
> normal). I didn't open a bug report, but probably should have so that it
> could be tracked/reported in the next release.
>
> jim
>
> ----------------------------------------------------------------
> James P. White Pagesmiths' home is http://www.pagesmiths.com
> Live free http://www.ushistory.org/franklin/quotable/quote04.htm
> Try Kawa, the Java-based Scheme http://www.gnu.org/software/kawa
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>