Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Jul 2002 20:24:45 -0400
From:      Garance A Drosihn <drosih@rpi.edu>
To:        Paul Richards <paul@freebsd-services.com>
Cc:        current@FreeBSD.ORG
Subject:   Re: Removing perl in make world
Message-ID:  <p05111740b94d39aab470@[128.113.24.47]>
In-Reply-To: <1025955773.881.29.camel@lobster.originative.co.uk>
References:  <1025862341.1573.40.camel@lobster.originative.co.uk> 	 <20020705095258.GC775@starjuice.net>	 <1025864161.1573.45.camel@lobster.originative.co.uk> <p05111730b94b6a140d74@[128.113.24.47]> <3D261EA4.ABC3AEC@mindspring.com> <p05111736b94be16e068e@[128.113.24.47]> <1025921146.881.16.camel@lobster.originative.co.uk>  <p05111738b94c05988039@[128.113.24.47]> <1025955773.881.29.camel@lobster.originative.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:42 PM +0100 7/6/02, Paul Richards wrote:
>On Sat, 2002-07-06 at 03:46, Garance A Drosihn wrote:
>>  At 3:05 AM +0100 7/6/02, Paul Richards wrote:
>>  >Let's start with a premise: No-one running current is using
>>  >it for anything other than developing FreeBSD.
>>
>>  This is assumption is too limiting.
>
>It shouldn't be. You're trying to defend a position that
>the project doesn't support.

It is too limiting.  I might be on current because I have my
*own* work I am doing on current.  You talk as if the only
development on -current is things that "other developers have
officially committed" to -current.  The fact that I have not
committed some work to -current does not give anyone the
right to go hog-wild with an 'rm' hanging off a blind 'find'
command.

It still boils down that you do not know why the files are
there.  I don't see why you're so determined to cause even
more hassle for people trying to "do the right thing" and
develop their changes on -current.

>The -current branch is for FreeBSD developers, or volunteers
>brave enough to test the -current branch.
>
>As such, don't be surprised if it wipes your hard disk clean.

Don't be surprised if you have even fewer -current testers.
Don't be surprised if we get to Novemeber of this year, and
-current is just as unstable and untested as it was last
year.  Don't be surprised if we never manage to release
-current, because it will never be sufficiently tested.

-- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05111740b94d39aab470>