I'm not familiar with doing diffs, so let me know if this isn't it
either. I'm using a CVS client (JCvs), so if this doesn't work, I'll go
to a command line.

- Robert

-----Original Message-----
From: Peter Donald [mailto:[EMAIL PROTECTED]] 
Sent: Sunday, May 19, 2002 4:11 AM
To: Avalon Developers List
Subject: Re: sending patches

If you could use a unified diff - ie don't forget the -u parameter that
would 
be even better as it makes it easier to see whats changed. (And it also
makes 
it near impossible to apply diffs to wrong file) 

;)

On Sun, 19 May 2002 19:07, Robert wrote:
> Ok, lets see if this works :-)
>
>
>
> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, May 19, 2002 3:57 AM
> To: Avalon Developers List
> Subject: Re: sending patches
>
> On Sun, 19 May 2002 18:51, Robert wrote:
> > Want me to send these updates via bugzilla? If so I assume that I
just
> > copy/paste the complete XML file into the 'Description' box, or want
>
> me
>
> > to send the XML file to the list?
>
> The best thing to do is to send unified diffs to the list. But make
sure
> they
> come as an attachment rather than inline (or else some mail clients
may
> mess
> them up).  Also, preferrably there would be one large patch rather
than
> lots
> of little ones. The easiest way to generate the patches is to do a
>
> cvs diff -u > docs.diff
>
> from base directory of whatever reposiotry you are working in.
>
> Look forwards to the diffs ;)

-- 
Cheers,

Peter Donald


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

Attachment: diffs.diff
Description: Binary data

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to