Re: Questions . . .

[Todd Denniston]

> Spencer Thomas wrote:
> 
> I have just set up a CVS server here in our shop (which was amazingly simple
> and CVS rocks the house), but I have two questions :
> 
> 1. Is there a way to make CVS "process" a file before it is actually
> "updated" (committed) back into the repository/module and only on specific
> files? One of my programmers is looking to run one of his "code formatters"
> on all of our Java source code as it goes back into the repository (so that
> everyone sees the same formatting).

http://www.cvshome.org/docs/manual/cvs_18.html#SEC165

Others can explain better why, although it can be done, doing this can be a
real headache.
(something to do with making cvs checkout the now updated version back into the
guy's sandbox, and change markers where there are no real content changes i.e.
conflicts out the wazoo)

http://mail.gnu.org/pipermail/info-cvs/2002-March/026478.html

http://mail.gnu.org/pipermail/info-cvs/2002-March/026400.html
http://mail.gnu.org/pipermail/info-cvs/2002-March/026406.html
http://mail.gnu.org/pipermail/info-cvs/2002-March/026439.html
http://mail.gnu.org/pipermail/info-cvs/2002-March/026491.html
just keep hitting the 'next message' links, this is a very long thread.

> 
> 2. Is there a way to make CVS force comments on commits? Right now it asks
> for a comment, but if you leave it blank it seems to be ok. I want CVS to
> refuse the commit until a comment is entered.
> 

see
http://mail.gnu.org/pipermail/info-cvs/2000-November/011106.html


-- 
______________________________________________________________________________
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power