Date: Tue, 24 Jul 2001 00:09:38 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: Greg Lehey <grog@FreeBSD.org>, Kris Kennaway <kris@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/libexec/atrun atrun.c Message-ID: <20010724000938.C49187@dragon.nuxi.com> In-Reply-To: <p0510100db7827da58818@[128.113.24.47]>; from drosih@rpi.edu on Mon, Jul 23, 2001 at 09:30:44PM -0400 References: <200107231205.f6NC5R526236@freefall.freebsd.org> <200107231103.f6NB3mi10592@freefall.freebsd.org> <200107231100.f6NB0Wm05549@freefall.freebsd.org> <20010724090813.M55779@wantadilla.lemis.com> <p0510100db7827da58818@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 23, 2001 at 09:30:44PM -0400, Garance A Drosihn wrote: > If you are questioning the log message, then the issue is "What > are log messages for?". The log message is supposed to give a > short but informative summary of what the change is. Not fully. Much more important (since I can do `cvs diff' if I really want to see the "what") is the _why_. In many cases the _why_ is obvious. But in many it is 100% apparent _why_ to the committer, but really no one else (including the committer) 6mo., 1 yr, 5 years later. > These log messages are informative, and it's hard to imagine how they > could be any shorter. Sounds like a good log message to me. In these particular cases I totally agree. Grog must have caught the "very boring post-USENIX weekend" bug or something... -- -- David (obrien@FreeBSD.org) 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?20010724000938.C49187>