Ok, I was using that scenario as if I was a commiter and did it all myself. With that in mind, it sounds like I am on target, correct?
-----Original Message----- From: Peter Royal [mailto:proyal@;apache.org] Sent: Thursday, October 24, 2002 3:52 PM To: Avalon Developers List Subject: Re: [OT] CVS and patches On Thursday, October 24, 2002, at 03:31 PM, Robert wrote: > LOL, I knew it had to be that simple. Unless I missed it I couldn't > find > a 'patch' command reference in the online cvs manual. It mentioned it > when doing the diff, but that was it. So, I would make my changes, do a > diff -u, then do patch -p0 < path.filename, which creates a new file I > take it(?), then commit the new file. Is that about right? you wouldn't do all the above... the submitter would make changes and do "diff -u", the recipient would then use the patch command to apply the diff to their own working tree and commit that into cvs. -pete -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
