From owner-cvs-all Fri Mar 9 6:31: 6 2001 Delivered-To: cvs-all@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id BDE2B37B718; Fri, 9 Mar 2001 06:31:01 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA14779; Sat, 10 Mar 2001 01:30:25 +1100 Date: Sat, 10 Mar 2001 01:30:14 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: Will Andrews , netch@netch.kiev.ua, Michael Haro , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/security/sudo Makefile distinfo In-Reply-To: <20010308081123.B84789@mollari.cthul.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Mar 2001, Kris Kennaway wrote: > On Thu, Mar 08, 2001 at 08:35:22AM -0500, Will Andrews wrote: > > On Thu, Mar 08, 2001 at 01:59:13PM +0200, Valentin Nechayev wrote: > > > Is it reasonable in any such case, make forced null commit with right > > > description? > > > > No. > > Yes. Misleading commit messages suck. I hate it when a port commit > does a different thing than it says in the commit message when I'm > trying to track down a change. Yes. But it's still not always easy to find the correct message when it's not for the original commit. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message