Except that it's not going to be an option once fully integrated...So whats
the point of adding it to 20+ config files to then remove it shortly 
afterwards? If people want to test it they know of the option now.

James


>
>Whilst you use pejorative terms such as "beta test" and "pet
>projects", from where I'm sitting it looks like the code will become
>part of -current RSN, and thereby part of 1.6.  As such, I'd like
>it documented in the GENERIC kernel configs - that way, everyone
>knows about it, and has the opportunity to enable it in their
>own kernels.
>
>Alistair
>
>On Wed, Sep 26, 2001 at 02:17:13PM -0400, James Chacon wrote:
>> In general beta test material that will become the replacement/default hasn't
>> been included in the GENERIC configs because the options are there simply for
>> the lifetime the option is beta. Otherwise should we be including everyones
>> pet projects as commented out options in GENERIC?
>> 
>> James
>> 
>> >
>> >Whatever - at the moment, NEW_PIPE should be documented in GENERIC kernel
>> >config files right now.
>> >
>> >Alistair
>> >
>> >On Wed, Sep 26, 2001 at 02:31:22AM -0700, Chuck Silvers wrote:
>> >> hi,
>> >> 
>> >> if we're going to make this the default, we should just remove the option
>> >> and have it no longer be optional.  if we're not confident enough in the
>> >> code to deconditionalize it, we shouldn't make it the default either.
>> >> 
>> >> personally I'd say wait a couple weeks and if there are no more
>> >> problems reported then make it non-optional.
>> >> 
>> >> -Chuck
>> >> 
>> >> 
>> >> On Wed, Sep 26, 2001 at 11:14:32AM +0200, Alistair Crooks wrote:
>> >> ...
>> >> > Could you add "#options \tNEW_PIPE" to the relevant GENERIC kernel
>> >> > configs (i.e. all of them), please?
>> >
>> >
>> >
>> >
>
>
>
>