RE: cvs commitinfo - remote access issues - enforced code beautification

[Austin Lauree]

Thanks for this tip Scott.  I wanted to enforce the use of a Header or Id 
keyword anyway.  :)

I verified it works for kkv expansion (default) and I confirmed that it does 
not work for kk non-expansion (which I commonly use when merging between 
branches).

Cheers,
-Lauree

-----Original Message-----
From: Thomas S. Urban [mailto:address@hidden
Sent: Wednesday, March 20, 2002 12:54 PM
To: Austin Lauree
Cc: CVS Info - Mailing List (E-mail)
Subject: Re: cvs commitinfo - remote access issues - enforced code
beautification

<snip>
Yeah, I've seem this with my commitinfo scripts.  I think if you ensure
that the files you are working in have CVS/RCS keywords in them (and
keyword expansion is not turned off for those files), the remote client
will get an updated version after the commit. Add a comment header to
all your files with $Id$ or similar in it.  Have your developers use
templates for code that have the keywords in them.
<snip>