From owner-cvs-all@FreeBSD.ORG Mon Oct 4 14:54:09 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEBD116A4CE; Mon, 4 Oct 2004 14:54:09 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE4CE43D45; Mon, 4 Oct 2004 14:54:09 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Mon, 04 Oct 2004 07:54:09 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0B4C35D04; Mon, 4 Oct 2004 07:54:09 -0700 (PDT) To: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: Your message of "Mon, 04 Oct 2004 16:40:41 +0200." Date: Mon, 04 Oct 2004 07:54:09 -0700 From: "Kevin Oberman" Message-Id: <20041004145409.0B4C35D04@ptavv.es.net> cc: cvs-src@FreeBSD.org cc: Ceri Davies cc: cvs-all@FreeBSD.org cc: src-committers@FreeBSD.org cc: Tim Robbins Subject: Re: cvs commit: src/bin/rm rm.1 rm.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 14:54:09 -0000 > From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) > Date: Mon, 04 Oct 2004 16:40:41 +0200 > Sender: owner-cvs-all@freebsd.org > > Ceri Davies writes: > > It didn't mention which standard, and I guess from the lack of citation > > that you have that information to hand either. > > And this is where you'd be wrong. Check the Austin Group mailing list > archives and the SCU Defect Report in Aardvark. This issue has been > discussed on and off since April 2003. As far as I can tell, the > resolution was that "the wording in the current version of the > standard does not allow this, but future versions will." Look! I might or might not care about the actual change, but this needs a REAL commit message. I don't really care if a change is right or wrong (or, more likely, somewhere in between), there is no excuse for a meaningless commit message. Please do a forced commit with a real log entry! Then we can get back to the discussion of its appropriateness. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634