From owner-cvs-all Sun Jul 26 17:28:02 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04697 for cvs-all-outgoing; Sun, 26 Jul 1998 17:28:02 -0700 (PDT) (envelope-from owner-cvs-all) Received: from localhost.my.domain (ppp6551.on.bellglobal.com [206.172.208.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04608; Sun, 26 Jul 1998 17:27:49 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id UAA29473; Sun, 26 Jul 1998 20:28:19 -0400 (EDT) (envelope-from tim) Message-ID: <19980726202819.A29443@zappo> Date: Sun, 26 Jul 1998 20:28:19 -0400 From: Tim Vanderhoek To: Bruce Evans , phk@critter.freebsd.dk, thepish@FreeBSD.ORG Cc: cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin/time time.1 time.c References: <199807241443.AAA05108@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807241443.AAA05108@godzilla.zeta.org.au>; from Bruce Evans on Sat, Jul 25, 1998 at 12:43:35AM +1000 Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Jul 25, 1998 at 12:43:35AM +1000, Bruce Evans wrote: > > >Furthermore, the energies wasted in this discussion should be redirected > >to more productive activities, like reviewing and handling PRs. > > OK, the patch was not suitable for committing verbatim, due to spelling > errors ("premissions"), style bugs (redeclaration of opt* ...) and > inconsistency of the new args with truss(1) and gnu time(1). Is no one going to bother fixing this? It seems to me, that given our occasional griping about Linux incompatibilities, we should not be introducing our own gratuitous incompatibilities. Unless I couple people object, I plan to fix this. As an added bonus, I'll even provide free spell-checking services to phk (I'm not sure I want to know what "premissions" are necessary to use these new facilities. :-( Beyond just being compatible, this will reduce bug reports from bash users "How come the -a and -f flags don't work for time(1)?" ...Once bash adds support for its own time(1)'s options, that is (already in newer versions??). [Please don't bother respond "I would prefer you took the options out." --- such responses will be conveniently ignored :-] -- This .sig is not innovative, witty, or profund.