From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Jeff Garzik <jgarzik@pobox.com>,
john slee <indigoid@higherplane.net>, Dan Kegel <dank@kegel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why can't Johnny compile?
Date: Sat, 16 Nov 2002 19:42:51 -0200 [thread overview]
Message-ID: <20021116214250.GQ24641@conectiva.com.br> (raw)
In-Reply-To: <20021116213732.GO24641@conectiva.com.br>
Em Sat, Nov 16, 2002 at 07:37:32PM -0200, Arnaldo C. Melo escreveu:
> Em Sat, Nov 16, 2002 at 04:04:05PM -0500, Jeff Garzik escreveu:
> > About the only thing WRT menuconfig I would be ok with is commenting out
> > majorly broken drivers until they are fixed...
>
> We have OBSOLETE, EXPERIMENTAL, why not BROKEN? 8)
>
> It would appear as "BROKEN waiting for someone to fixme"
If, like for EXPERIMENTAL, BROKEN is selected by the user, or better,
by a developer wanting to fix what is broken.
- Arnaldo
next prev parent reply other threads:[~2002-11-16 21:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 5:35 Why can't Johnny compile? Dan Kegel
2002-11-16 5:49 ` Jeff Garzik
2002-11-16 6:04 ` Patrick Finnegan
2002-11-16 6:10 ` Jeff Garzik
2002-11-16 6:15 ` William Lee Irwin III
2002-11-17 5:34 ` Ralf Baechle
2002-11-16 9:47 ` Kai Henningsen
2002-11-16 14:37 ` Arnaldo Carvalho de Melo
2002-11-16 15:11 ` john slee
2002-11-16 6:23 ` Arnaldo Carvalho de Melo
2002-11-16 19:14 ` Nathan
2002-11-16 21:04 ` Jeff Garzik
2002-11-16 21:37 ` Arnaldo Carvalho de Melo
2002-11-16 21:42 ` Arnaldo Carvalho de Melo [this message]
2002-11-16 23:51 ` Alan Cox
2002-11-17 0:09 ` Dan Kegel
2002-11-17 0:08 ` romieu
2002-11-17 3:18 ` Patrick Finnegan
2002-11-17 0:18 ` Nathan
2002-11-17 0:43 ` Alan Cox
2002-11-18 21:02 ` Bill Davidsen
2002-11-18 23:12 ` Alan Cox
2002-11-19 16:30 ` Bill Davidsen
2002-11-19 16:36 ` Jeff Garzik
2002-11-19 17:29 ` Alan Cox
2002-11-19 18:01 ` David G Hamblen
2002-11-19 19:34 ` Alan Cox
2002-11-17 1:34 ` Adam Kropelin
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=20021116214250.GQ24641@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=dank@kegel.com \
--cc=indigoid@higherplane.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.