From owner-freebsd-current Wed Apr 26 1:56:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id D38D137B569 for ; Wed, 26 Apr 2000 01:56:54 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Wed, 26 Apr 2000 03:56:45 -0500 From: Richard Wackerbarth To: Doug Barton Subject: Re: Archive pruning Date: Wed, 26 Apr 2000 03:56:44 -0500 X-Mailer: KMail [version 1.1.41] Content-Type: text/plain References: <00042515302702.02802@nomad.dataplex.net> <390693A0.509C3134@gorean.org> In-Reply-To: <390693A0.509C3134@gorean.org> Cc: current@freebsd.org MIME-Version: 1.0 Message-Id: <00042603564400.06932@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000, you wrote: > Any further discussion from you on this point that doesn't include code > is totally and completely without value. You haven't proven the value of > your suggestion to _anyone's_ satisfaction, so no one is going to do it > for you. So if you're not willing to actually do it, please let it drop. You are correct that I "haven't proven" yet. Much of this is because the audience doesn't relate to the problem because they don't see themselves directly impacted by it. However, they are paying for it every time they use cvsup or cvs. That's the trouble with this developer community. They see EVERYTHING as WRITING CODE and "adding on". This is not about writing code. The code already exists. I am just advocating using it in a different way. As for the actual "doing", I'm quite willing to do to actual "legwork" that results from the change. But the change is a fundamental change in the way the organization "does business". Unless the organization makes a change, there is nothing to do. I think that it is just a matter of time until the matter gets raised by yet another person as the underlying problem gets more acute. I'll sit back and wait... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message