[LMH]Re: [Lispm-cvs] CVS update: e3/docs/ssdn2

James A. Crippen james@unlambda.com
Tue Apr 23 20:48:00 2002


Public humiliation time!

emmanuel@kappa.unlambda.com writes:

> Date:	Sunday April 21, 2002 @ 22:49
> Author:	emmanuel
> 
> Update of /home/cvsroot/e3/docs/ssdn2
> In directory kappa:/tmp/cvs-serv20143/e3/docs/ssdn2
> 
> Modified Files:
> 	ssdn2.tex 
> Log Message:

No log message!  Shame! ^_^

It's too late to do anything about it (short of hand editing the CVS
repo).  But remember in the future.  Even if you just do a stupid
one-liner change (like putting in an extra space in indentation)
please write a log!

By default CVS will use your current editor $EDITOR and let you write
a log entry.  You can also use the command line to do so, but it's
inconvenient (because you have to escape newlines).

The log messages are for humans.  Make them readable.  CVS itself
doesn't give a shit what you write in the logs, you could even write
nasty things about CVS in them.  But the developers need to know
what's going on in changes, not just now but in the future as well.
Any file's log can be called up with a single command, and developers
can use this to track changes long since past.  (Try 'cvs log' for
fun.)

'james

-- 
James A. Crippen <james@unlambda.com> ,-./-.  Anchorage, Alaska,
Lambda Unlimited: Recursion 'R' Us   |  |/  | USA, 61.20939N, -149.767W
Y = \f.(\x.f(xx)) (\x.f(xx))         |  |\  | Earth, Sol System,
Y(F) = F(Y(F))                        \_,-_/  Milky Way.