From: Adrian Bunk <bunk@stusta.de>
To: Radoslaw AstralStorm Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3-mm3 question
Date: Fri, 29 Jul 2005 12:57:04 +0200 [thread overview]
Message-ID: <20050729105704.GC3563@stusta.de> (raw)
In-Reply-To: <20050729025034.2b58d34e.astralstorm@gorzow.mm.pl>
On Fri, Jul 29, 2005 at 02:50:34AM +0200, Radoslaw AstralStorm Szkodzinski wrote:
> On Thu, 28 Jul 2005 22:42:38 +0200
> Adrian Bunk <bunk@stusta.de> wrote:
>
>
> > I'm surprised that you are that much concerned about compile errors when
> > using a kernel that might regularly exchange the contents of /dev/hda
> > and /dev/null .
> >
> These bugs don't happen too often in reality.
> Just please don't be malicious and add this kind of code deliberately. :)
>
> Every build breaker wastes my precious time to fix it.
> That's compulsive/obsessive in some way. ;)
>...
Someone has to test it.
Andrew already wastes some of his precious time for testing before
releasing a -mm kernel, but this doesn't catch every compile error.
If a -mm kernel doesn't compile for you, you can:
- apply a patch if it is already available
- fix it yourself
- wait for the next -mm
One of the purposes of -mm kernels is actually to find compile errors.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-07-29 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 17:43 2.6.13-rc3-mm3 question Radoslaw AstralStorm Szkodzinski
2005-07-28 17:55 ` Andrew Morton
2005-07-28 18:31 ` Radoslaw AstralStorm Szkodzinski
2005-07-28 20:42 ` Adrian Bunk
2005-07-29 0:50 ` Radoslaw AstralStorm Szkodzinski
2005-07-29 10:57 ` Adrian Bunk [this message]
2005-07-29 6:55 ` Matthias Urlichs
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 8:39 Chuck Ebbert
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=20050729105704.GC3563@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=astralstorm@gorzow.mm.pl \
--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.