From: Randy Dunlap <rdunlap@xenotime.net>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Adrian Bunk <bunk@stusta.de>, Jeff Garzik <jeff@garzik.org>,
Gabriel C <crazy@pimpmylinux.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus
Date: Thu, 19 Jul 2007 08:31:09 -0700 [thread overview]
Message-ID: <20070719083109.13b2ab56.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707190523001.19216@localhost.localdomain>
On Thu, 19 Jul 2007 05:25:30 -0400 (EDT) Robert P. J. Day wrote:
> On Thu, 19 Jul 2007, Stefan Richter wrote:
>
> > Robert P. J. Day wrote:
> > > On Thu, 19 Jul 2007, Adrian Bunk wrote:
> > >
> > > ...
> > >> I would consider it more ugly to special case this and that in the
> > >> kconfig code when plain dependencies already offer exactly the same
> > >> functionality...
> > >
> > > well, this is the *third* time i've proposed adding this kind of
> > > feature so, at this point, i've really given up caring about it. if
> > > someone wants to do this, have at it. i have better things to do than
> > > to keep suggesting it and getting nowhere with it.
> >
> > For better or worse, it can often be observed that feature requests
> > don't set anything in motion until a first patch is sent. Even a
> > patch that is far from perfect can get things going really quickly.
> > (If the requested feature makes sense to other people.)
>
> i *did* submit a preliminary patch once upon a time, and it
> (predictably) went nowhere. so, if someone else wants to pick this up
> and do something with it, you have my blessing. life's too short to
> keep wasting time on this.
I think that Stefan means a patch to the kconfig source code,
not the the Kconfig files. Good luck. I'd still like to see it.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-07-19 15:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 20:18 Gabriel C
2007-07-18 20:23 ` Robert P. J. Day
2007-07-18 20:40 ` Randy Dunlap
2007-07-18 20:44 ` Robert P. J. Day
2007-07-18 20:45 ` Jeff Garzik
2007-07-18 20:51 ` Robert P. J. Day
2007-07-18 21:09 ` Adrian Bunk
2007-07-18 21:18 ` Robert P. J. Day
2007-07-19 5:47 ` Adrian Bunk
2007-07-19 7:33 ` Robert P. J. Day
2007-07-19 8:42 ` Stefan Richter
2007-07-19 9:25 ` Robert P. J. Day
2007-07-19 13:53 ` Stefan Richter
2007-07-19 15:31 ` Randy Dunlap [this message]
2007-07-19 16:19 ` Robert P. J. Day
2007-07-19 22:05 ` Simon Arlott
2007-07-19 22:28 ` Robert P. J. Day
2007-08-31 17:25 ` Randy Dunlap
2007-08-31 17:23 ` Robert P. J. Day
2007-08-31 18:06 ` Jeff Garzik
2007-08-31 19:29 ` Jan Engelhardt
2007-08-31 20:16 ` Randy Dunlap
2007-08-31 21:00 ` Robert P. J. Day
2007-08-31 21:25 ` Randy Dunlap
2007-08-31 20:49 ` Robert P. J. Day
2007-08-31 22:01 ` Jeff Garzik
2007-08-31 22:10 ` Robert P. J. Day
2007-09-01 10:44 ` Robert P. J. Day
2007-09-01 12:49 ` Sam Ravnborg
2007-09-01 12:56 ` Robert P. J. Day
2007-07-18 21:28 ` Robert P. J. Day
2007-07-18 20:52 ` Randy Dunlap
2007-07-18 20:48 ` Gabriel C
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=20070719083109.13b2ab56.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bunk@stusta.de \
--cc=crazy@pimpmylinux.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®