From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Adrian Bunk <bunk@fs.tum.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.8-rc1
Date: Mon, 12 Jul 2004 22:28:18 +0200 [thread overview]
Message-ID: <4d8e3fd304071213287b995ae9@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407120940360.1764@ppc970.osdl.org>
On Mon, 12 Jul 2004 09:43:54 -0700 (PDT), Linus Torvalds
<torvalds@osdl.org> wrote:
>
>
> On Mon, 12 Jul 2004, Adrian Bunk wrote:
> >
> > The Linux kernel development process isn't that much formalized. But if
> > someone finds a serious new problem in a -rc kernel a fix will usually
> > go into the next -rc.
>
> Indeed.
>
> The whole _point_ of -rc kernels is to find silly problems.
>
> Trying to have a release mechanism for -rc kernels in order to avoid some
> problems in them would kind of defeat the point. The -rc kernels are there
> to encourage people who wouldn't want to just take a daily shapshot to
> tell us when we break things - and clearly it's working ;)
Again, I'm really not saying that is not working ;-),
I just think that the process could be improved using the tools we
already have available.
> (There's also a totally nontechnical point to -rc kernels: it's a way to
> tell people to calm down a bit. Usually we have a backlog that gets filled
> up after a kernel release, and then with the -rc kernels people usually
> slow down feeding non-critical stuff to me. At least a bit)
>
--
paoloc.doesntexist.org
next prev parent reply other threads:[~2004-07-12 20:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 18:29 Linux 2.6.8-rc1 Linus Torvalds
2004-07-11 23:00 ` [PATCH] edd (Re: Linux 2.6.8-rc1) Randy.Dunlap
2004-07-12 3:02 ` Adrian Bunk
2004-07-12 4:49 ` Matt Domsch
2004-07-12 5:21 ` Randy.Dunlap
2004-07-12 9:26 ` Linux 2.6.8-rc1 Matthias Andree
2004-07-12 18:54 ` Martin Schlemmer
2004-07-12 9:34 ` Paolo Ciarrocchi
2004-07-12 15:42 ` Adrian Bunk
2004-07-12 15:56 ` Paolo Ciarrocchi
2004-07-12 16:34 ` Adrian Bunk
2004-07-12 16:43 ` Linus Torvalds
2004-07-12 20:28 ` Paolo Ciarrocchi [this message]
2004-07-12 20:22 ` Paolo Ciarrocchi
2004-07-13 20:54 ` cliff white
2004-07-12 21:08 ` Horst von Brand
2004-07-12 11:30 ` is_highmem() and WANT_PAGE_VIRTUAL (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 13:51 ` Andy Whitcroft
2004-07-12 14:23 ` Geert Uytterhoeven
2004-07-12 12:01 ` Linux 2.6.8-rc1 Geert Uytterhoeven
2004-07-12 13:18 ` OGAWA Hirofumi
2004-07-12 13:25 ` Geert Uytterhoeven
2004-07-12 14:02 ` OGAWA Hirofumi
2004-07-12 13:23 ` struct_cpy() and kAFS (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 18:11 ` Andrew Morton
2004-07-12 18:23 ` Christoph Hellwig
2004-07-12 18:40 ` Andrew Morton
2004-07-13 10:14 ` David Howells
2004-07-12 23:49 ` Linux 2.6.8-rc1 (compile stats) John Cherry
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=4d8e3fd304071213287b995ae9@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.