From: Gabriel C <nix.or.die@googlemail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] IP_VS should depend on EXPERIMENTAL ?
Date: Fri, 20 Jul 2007 14:32:04 +0200 [thread overview]
Message-ID: <46A0AB44.70009@googlemail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707200818010.12187@localhost.localdomain>
Robert P. J. Day wrote:
> On Fri, 20 Jul 2007, Gabriel C wrote:
>
>> Robert P. J. Day wrote:
>>> On Fri, 20 Jul 2007, Gabriel C wrote:
>>>
>>>> Hi,
>>>>
>>>> IP_VS has :
>>>>
>>>> ..
>>>>
>>>> tristate "IP virtual server support (EXPERIMENTAL)"
>>>>
>>>> ..
>>>>
>>>> but it does not depend on EXPERIMENTAL.
>>>>
>>>>
>>>> Signed-off-by: Gabriel Craciunescu <nix.or.die@googlemail.com>
>>>>
>>>> ---
>>>>
>>>> net/ipv4/ipvs/Kconfig | 2 +-
>>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/net/ipv4/ipvs/Kconfig b/net/ipv4/ipvs/Kconfig
>>>> index 09d0c3f..3c594ec 100644
>>>> --- a/net/ipv4/ipvs/Kconfig
>>>> +++ b/net/ipv4/ipvs/Kconfig
>>>> @@ -3,7 +3,7 @@
>>>> #
>>>> menuconfig IP_VS
>>>> tristate "IP virtual server support (EXPERIMENTAL)"
>>>> - depends on NETFILTER
>>>> + depends on NETFILTER && EXPERIMENTAL
>>>> ---help---
>>>> IP Virtual Server support will let you build a high-performance
>>>> virtual server based on cluster of two or more real servers. This
>>> there's maturity-level inconsistency like that in a few places, like
>>> when stuff is tagged as EXPERIMENTAL, but labelled as OBSOLETE:
>>>
>> [ a lot examples ]
>>
>> I know that and there are a lot more things depending on
>> 'EXPERIMENTAL' and not having EXPERIMENTAL visible all over the tree
>> but that patch I've made for the _net_ part got NACK'ed while your
>> maturity idea and I rm -rf'ed all the other.
>>
>> This one has a missing depends on EXPERIMENTAL while saying it is.
>>
>> So *could* we please stop this maturity stuff for now ? I don't see
>> it in .23 nor .24 if at all.
>
> this has *nothing* to do with the aforementioned maturity levels. i
> understand entirely the inconsistency above. what i'm suggesting is
> that it might very well be more appropriate to *drop the dependency*
> rather than munge the prompt to add the qualifier.
This is a thing the author/maintainer/subsystem maintainer should and need do.
They know when something is not EXPERIMENTAL anymore.
>
> i think it's safe to say that there's *piles* of stuff in the Kconfig
> files that is still saddled with an EXPERIMENTAL dependency that's
> been around for years and has stabilized nicely.
I agree with you , there may be a lot things are marked EXPERIMENTAL but aren't anymore.
>i mean, seriously,
> is IP virtual server support still "experimental" in any way?
>
> rday
Gabriel
next prev parent reply other threads:[~2007-07-20 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 11:44 [PATCH] IP_VS should depend on EXPERIMENTAL ? Gabriel C
2007-07-20 11:59 ` Robert P. J. Day
2007-07-20 12:17 ` Gabriel C
2007-07-20 12:21 ` Robert P. J. Day
2007-07-20 12:32 ` Gabriel C [this message]
2007-07-20 13:04 ` Robert P. J. Day
2007-07-20 12:11 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A0AB44.70009@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rpjday@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).