public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Radoslaw AstralStorm Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3-mm3 question
Date: Thu, 28 Jul 2005 22:42:38 +0200	[thread overview]
Message-ID: <20050728204238.GC4790@stusta.de> (raw)
In-Reply-To: <20050728203133.0a03dbda.astralstorm@gorzow.mm.pl>

On Thu, Jul 28, 2005 at 08:31:33PM +0200, Radoslaw AstralStorm Szkodzinski wrote:
> On Thu, 28 Jul 2005 10:55:51 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>...
> > There are always glitches, I'm afraid.
> 
> But there could be less build breakers at least.

The -mm kernels are the result of mixing the latest developments from a 
dozen subsystem trees with a few hundred random patches from 
linux-kernel resulting in the most unstable kernel available. [1]

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 .

cu
Adrian

[1] that's a bit exaggerated and not meant against Andrew

-- 

       "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


  reply	other threads:[~2005-07-28 20:44 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 [this message]
2005-07-29  0:50       ` Radoslaw AstralStorm Szkodzinski
2005-07-29 10:57         ` Adrian Bunk
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=20050728204238.GC4790@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox