On Thu, Oct 13, 2005 at 10:18:54AM -0500, Eric Anderson wrote: > Craig Rodrigues wrote: > >On Thu, Oct 13, 2005 at 08:27:50AM -0500, Eric Anderson wrote: > > > >>Thanks - great suggestion! I'll do that. Any ideas how to remove the > >>FBSDID line jitter from the patches? > > > > > >When you check out the files from CVS, do not expand the CVS keywords by > >doing: cvs co -kk > > So, this brings up a quick question: what methods do most developers > use when doing things like this? I looked in the developer's handbook, > but didn't see any quick guide on a good method. Do you keep the local > cvs repo up to date, then check it out, make changes, etc? How do you > do the diffs, and track all the changes, while testing too? I'd like to > kind of copy someone else's known-functional method instead of coming up > with my own. The easiest way with existing tools is to work in a copy checked out from a locally mirrored CVS repository. You can then use "cvs diff" to generate diffs. If you add new files, you will need to hack the CVS metadate yourself if you want to use "cvs diff -N" to include those files. That's ugly, but it should work. Try a test repo to see what the changes to CVS/Entries would look like. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:45 UTC