Re: use of cut in guile-doc-snarf

["Greg J. Badros" <gjb at cs dot washington dot edu>]

Michael Livshin <mlivshin@bigfoot.com> writes:

> "Greg J. Badros" <gjb@cs.washington.edu> writes:
> 
> > The log message claims that the lines were intended to be trimmed to 512 
> > characters:
> > 
> > revision 1.12
> > date: 2000/05/22 14:03:37;  author: cmm;  state: Exp;  lines: +3 -1
> > * guile-doc-snarf.in: put the preprocessed file through sed to
> > trim all lines to 512 chars.  I hope it doesn't break anybody's
> > shell.  we'll see.
> 
> and I've later fixed the ChangeLog.  is there a way to retroactively
> fix CVS logs?  I don't think there should be, actually.  one of the
> reasons why ChangeLog is the definitive source for such info...

Yes, they can and should be updated (if I want a history of what changed 
on a specific file, its log is what I go to, if I want a history of how
the project changed, the ChangeLog (automatically-generated or manually
maintained) is what I go to).

cvs admin -mREV:MSG
     Replace the log message of revision REV with MSG.

> [ oh, and cut -c1-1023 works on HP, which (for me) means it's portable 
>   all right, unless someone says it doesn't work on something horrible 
>   like Ultrix or DG-UX.  so I'll commit the change shortly. ]

Good!

Greg