Date: Sat, 14 Dec 1996 16:05:49 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: dg@root.com Cc: joerg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/kern uipc_usrreq.c Message-ID: <199612141505.QAA27073@uriah.heep.sax.de> In-Reply-To: <199612141445.GAA02049@root.com> from David Greenman at "Dec 14, 96 06:45:45 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As David Greenman wrote: > > Branch: sys/kern RELENG_2_2 > > Modified: sys/kern uipc_usrreq.c > > Log: > > YAMFC > > You know, log messages like this make it extremely difficult to know > what has been brought in to 2.2 and what has not. I know Poul started this > precedent, but it was a bad one that I really wish would stop. It basically means "Everything merged from -current up to the date of the checked out tree the diff has been taken against." The checked out tree is /c/src, and is upgraded (manually) via CTM, so it lags around 6 or 8 hours behind the current date/time. It's at least possible to compare the date of the merge and the date of the most recent change right before. I agree that it's not a very meaningful message, but it's about the only way one could handle mass-merges of this amount if the release engineer does also have a day job -- it saves quite some hours since the release engineering can concentrate on reviewing diffs and log messages, while the actual commit is handled by a script. Anyway the committs you've seen by now are probably the last ones that happen to have this commit message. See my other mail. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612141505.QAA27073>