public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: john slee <indigoid@higherplane.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Why can't Johnny compile?
Date: Fri, 15 Nov 2002 21:35:59 -0800	[thread overview]
Message-ID: <3DD5D93F.8070505@kegel.com> (raw)

john slee <indigoid@higherplane.net> wrote:
> On Thu, Nov 14, 2002 at 10:58:09PM -0500, Patrick Finnegan wrote:
>> It'd be nice if people simply tried compiling a patched kernel (all
>> affected modules) before they submitted the patch, I'm betting you'd catch
>> a lot of typos.  Also, compiling _everything_, even as a module, at
>> least once before sumbitting the patch would probably help.
> 
> thats fine if there is an all-compiling kernel release out there.  right
> now 2.5-bk is far from it.  last i checked allmodconfig (a couple of
> days ago) there was major breakage all over llc, scsi, video, sound, ...
> which kinda masks any breakages you might have introduced. 

Hrmph.  Y'know, maybe it's time for us to collectively put our
feet down, get 2.5-linus to the point where everything compiles,
and keep it there.  After all, we are supposedly trying to
*stabilize* 2.5.  It isn't stable if it doesn't compile...

- Dan


             reply	other threads:[~2002-11-16  5:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-16  5:35 Dan Kegel [this message]
2002-11-16  5:49 ` Why can't Johnny compile? 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
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=3DD5D93F.8070505@kegel.com \
    --to=dank@kegel.com \
    --cc=indigoid@higherplane.net \
    --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