info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: controlling/checking comments in commits


From: Mark D. Baushke
Subject: Re: controlling/checking comments in commits
Date: Wed, 24 Jan 2007 00:10:17 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sinan Kalkan <address@hidden> writes:
> i'd like to ask whether it is possible:
> 
> 1- to disallow empty comments in commits and/or

Yes, you could write a verifymsg script which denied a commit for which
the log message was empty. You would probably also want to disallow just
typing whitespace or '.' as long as you are at it.

> 2- to force getting separate comments for each file that become
> committed.

Well, if you are avoiding client/server commits, then you could get
per-directory log messages. If there is more than one file per directory
being changed, then there would be no way to enforce a per-file commit
log message.

I am not sure I think it is wise to have a different log message for
every commit in any case.

> as far as i've learned, it is possible to 'install' scripts of our
> own before or after commit but i've not figured out a way to get
> information about the comments nor how to force separate comments
> for each file.

Read: http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_18.html#SEC172

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFFtxRpCg7APGsDnFERAiOSAJwJXuCLV5/iNJclrt8rqe2y52p4jgCgvKaC
2c6mlqFBisrUfabhidbkBdE=
=eAM9
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]