RE: Showing diff in commit message editor

[Greg A. Woods]

[ On Friday, January 9, 2004 at 09:40:15 (-0500), Jim.Hyslop wrote: ]
> Subject: RE: Showing diff in commit message editor
>
> This is simply a matter of training yourself to perform all the necessary
> steps, in the correct order. 
> 
> Except for the most trivial changes to files you *know* are up to date, the
> commit procedure is not a single command, it is a sequence of commands that
> cannot be automated, because of the thought processes required by the humans
> at each step:
> 
> cvs update
> Sanity check: rebuild if something was out of date
> cvs diff: ensure that the changes are what you expected (for example, did
> you remember to remove that debugging printf statement?)
> cvs commit
> 
> Unfortunately, too many people skip the first three steps.

Indeed.

I find it helps to use tools integrated right into my text editor to
drive both CVS and all the tasks that surround its use.

I use Emacs of course and the tool of choice for many Emacs users is
PCL-CVS.  It turns Emacs into a CVS front-end application that can also
edit files.  :-)

-- 
                                                Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <address@hidden>
Planix, Inc. <address@hidden>          Secrets of the Weird <address@hidden>