[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: controlling/checking comments in commits
From: |
Jim Hyslop |
Subject: |
Re: controlling/checking comments in commits |
Date: |
Sun, 28 Jan 2007 20:32:57 -0500 |
User-agent: |
Mozilla Thunderbird 1.0.6 (Windows/20050716) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark D. Baushke wrote:
> 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.
Or typing 'asdfasdf' or 'qwertyiop' or '123' or 'blah' or 'changes' or
'latest' or...
IOW, it's not worth it.
>>>2- to force getting separate comments for each file that become
>>>committed.
Yikes!! Don't do it. Comments should reflect the high-level overview of
what was done, not nitty-gritty details of what precise changes were
made to each file (use `cvs diff` for that!). I can't count the number
of times I have committed dozens of files at once, all because of one
conceptual change to the source.
- --
Jim Hyslop
Dreampossible: Better software. Simply. http://www.dreampossible.ca
Consulting * Mentoring * Training in
C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFFvU7JLdDyDwyJw+MRAnhpAKDL1F7BULnYWdjb2wWFKYPZoZO2sQCeO2bu
tLg0X6/Z1metX5Vu3aOJM4A=
=GINs
-----END PGP SIGNATURE-----