mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Amanda McPherson <amanda@amcpherson.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH, RFC] A development process document
Date: Wed, 30 Jul 2008 14:56:00 -0600	[thread overview]
Message-ID: <20080730145600.7b61a43a@bike.lwn.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0807301307060.26427@twin.jikos.cz>

On Wed, 30 Jul 2008 13:09:13 +0200 (CEST)
Jiri Kosina <jkosina@suse.cz> wrote:

> On the other hand, the drivers for completely new hardware (that has
> been totally unsupported by the kernel previously, so there is no
> possibility for introducing regressions) are still allowed even after
> -rc1, right? 

Clearly it's been known to happen (can you say GRU?).  But I don't know
that has ever really been adopted as an "official" policy.  My
preference would be to lay down the merge window rules as a fairly firm
thing rather than suggest to people that there might be ways to slip
around them sometimes.  But, certainly, I'm not tied to that if we want
to send a different message.

Thanks,

jon

  parent reply	other threads:[~2008-07-30 20:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 20:30 Jonathan Corbet
2008-07-30  7:15 ` Andrew Morton
2008-07-30 18:05   ` Jonathan Corbet
2008-07-30 11:09 ` Jiri Kosina
2008-07-30 16:05   ` Takashi Iwai
2008-07-30 20:56   ` Jonathan Corbet [this message]
2008-07-30 21:30     ` Roland Dreier
2008-07-30 21:38       ` Jiri Kosina
2008-07-31  6:23 ` Alex Chiang
2008-07-31 16:17   ` Jonathan Corbet
2008-07-31 17:49     ` Daniel Barkalow
2008-07-31 17:57       ` Randy.Dunlap
2008-08-01 10:35         ` Stefan Richter
2008-08-01 16:52           ` Daniel Barkalow
2008-07-31 12:22 ` Jochen Voß
2008-07-31 16:30   ` Jonathan Corbet
2008-07-31 23:45 ` Jake Edge

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=20080730145600.7b61a43a@bike.lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=amanda@amcpherson.com \
    --cc=jkosina@suse.cz \
    --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

all inboxes | Powered by JetHome®