From owner-cvs-sys Sat Dec 14 07:24:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA06652 for cvs-sys-outgoing; Sat, 14 Dec 1996 07:24:04 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA06582; Sat, 14 Dec 1996 07:22:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA07014; Sat, 14 Dec 1996 16:22:45 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA05211; Sat, 14 Dec 1996 16:21:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id QAA27073; Sat, 14 Dec 1996 16:05:50 +0100 (MET) From: J Wunsch Message-Id: <199612141505.QAA27073@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/kern uipc_usrreq.c To: dg@root.com Date: Sat, 14 Dec 1996 16:05:49 +0100 (MET) Cc: joerg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612141445.GAA02049@root.com> from David Greenman at "Dec 14, 96 06:45:45 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-cvs-sys@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. ;-)