From owner-freebsd-arch Fri May 3 0:27:59 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DB5AA37B681; Fri, 3 May 2002 00:27:38 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g437RCQ4011646; Fri, 3 May 2002 09:27:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Terry Lambert , arch@FreeBSD.org Subject: Re: savcore dump names? In-Reply-To: Your message of "Thu, 02 May 2002 18:23:36 EDT." Date: Fri, 03 May 2002 09:27:12 +0200 Message-ID: <11645.1020410832@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , John Baldwin writes: >So it is acceptable to come in and break existing functionality because >you don't feel like finishing the job? I mean, come on, you had to do >the work to change the code to make it break existing functionality. >It would have been _less_ work to have left the code that respected >minfree, etc. and kept the filenames the same as it is. > >IMO, it is unacceptable to come in and break stuff and then say it's >not your problem to fix it. Sometimes you have to break the eggs to make an omelette. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message