From owner-freebsd-hackers Sun Jan 21 21:33:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id E9C6637B400 for ; Sun, 21 Jan 2001 21:33:05 -0800 (PST) Received: (qmail 44366 invoked by uid 1001); 22 Jan 2001 15:33:01 +1000 X-Posted-By: GJB-Post 2.11 18-Jan-2001 X-Operating-System: FreeBSD 4.1-RELEASE i386 X-URL: http://www.gbch.net X-Image-URL: http://www.gbch.net/gjb/img/gjb-auug048.gif X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 X-PGP-Public-Key: http://www.gbch.net/gjb/gjb-pgpkey.asc Message-Id: Date: Mon, 22 Jan 2001 15:33:00 +1000 From: Greg Black To: Sergey Babkin Cc: dan@langille.org, freebsd-hackers@FreeBSD.ORG Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etccrontab) References: <200101212035.JAA19266@ducky.nz.freebsd.org> <3A6B85B2.3A10195C@bellatlantic.net> In-reply-to: <3A6B85B2.3A10195C@bellatlantic.net> of Sun, 21 Jan 2001 19:58:26 EST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin wrote: > It still can be backed out. Well, what are you waiting for? Back it out. Listen to what people are saying and then maybe propose something that takes into account their concerns. To make this point a little more clearly -- the fact that Matt Dillon, who is no fool, and you have wildly divergent ideas on the appropriate/correct method to determine when to do things is further evidence (as if any were needed) that this is not a trivial thing to get right. First, people have to agree on what is right and we're not there yet. Please take note of what people are saying, stop the silly protests about your failure to be convinced by other people's arguments, and recognise that you don't have a special line to the One True Way. Finally, in reference to the confusion over POLA, get something straight: the people we must take most care not to astonish are current users of FreeBSD; after them, we can consider users who are migrating from other Unix variants. The fact that others may do things differently is not, of itself, an argument to take a wild jump into the darkness here. The continued, predictable, behaviour of cron is important to users and cannot be just played about with at your whim, and this is especially true when you don't even have support for the so-called solution you have proposed. Back it out. Do it now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message