Date: Fri, 20 Nov 1998 09:28:13 +1030 From: Greg Lehey <grog@lemis.com> To: cvs-all@FreeBSD.ORG Subject: Categorizing commit messages Message-ID: <19981120092813.H467@freebie.lemis.com>
next in thread | raw e-mail | index | archive | help
I suppose about 100 commit messages get sent out every day. We're all
exhorted to read every one of them. I try to do that, but I'm sure I
miss some important stuff. Looking at what I've had over the last few
months, I'd estimate the following breakdown:
1. Typos, cosmetic changes. About 20%
2. Minor bug fixes, style changes. About 30%.
3. Major bug fixes. About 10%
4. New functionality in existing software. About 5%.
5. New software (mainly ports, but also things like CAM, etc). About
35%.
These differences are relatively easy to recognize, but you have to
read *all* the messages to find out. How about a field in the commit
message which says what kind of change it is? This is more important
than just being able to find out what has changed: documentation,
including release notes, also depends on it.
Comments? Ideas?
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981120092813.H467>