From: Dan Kegel <dank@kegel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
Jeff Garzik <jgarzik@pobox.com>,
john slee <indigoid@higherplane.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why can't Johnny compile?
Date: Sat, 16 Nov 2002 16:09:22 -0800 [thread overview]
Message-ID: <3DD6DE32.60503@kegel.com> (raw)
In-Reply-To: 1037490677.24843.7.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
>>>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...
>
> Thats basically what "OBSOLETE" is
So how 'bout this:
* mark all drivers that don't compile OBSOLETE. That keeps us from
trying to fix drivers without having hardware to test them.
Anyone with proper hardware is invited to fix the drivers and then
mark them non-OBSOLETE.
* make 'curyesconfig' and 'curmodconfig' compile everything that isn't OBSOLETE
* fix anything left over that keeps 'make curyesconfig'
and 'make curmodconfig' from compiling
* maintainers try to not forward any patches to Linux that
cause 'make curyesconfig' or 'make curmodconfig' not build
* OSDL does nightly 'curyesconfig' and 'curmodconfig builds from
Linus's tree, and mails linux-kernel a link to the build log
along with whether it succeeded or failed
That would give maintainers quick feedback about whether they'd
broken some obscure part of Linus's tree...
- Dan
next prev parent reply other threads:[~2002-11-16 23:40 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
2002-11-16 23:51 ` Alan Cox
2002-11-17 0:09 ` Dan Kegel [this message]
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=3DD6DE32.60503@kegel.com \
--to=dank@kegel.com \
--cc=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox