public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Christoph Lameter <clameter@sgi.com>,
	linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: Conditionals for development tests and output
Date: Sat, 2 Jun 2007 10:48:21 -0700	[thread overview]
Message-ID: <20070602104821.d2d8d668.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070602144348.GD5500@stusta.de>

On Sat, 2 Jun 2007 16:43:48 +0200 Adrian Bunk <bunk@stusta.de> wrote:

> And your approach could easily result in code paths never tested in 
> -mm or -rc kernels exploding in the actual release.

yep, we need to ensure that DEVELKERNEL gets turned off a few weeks
before final release.

  reply	other threads:[~2007-06-02 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02  4:17 Conditionals for development tests and output Christoph Lameter
2007-06-02 14:43 ` Adrian Bunk
2007-06-02 17:48   ` Andrew Morton [this message]
2007-06-03 16:27     ` Matt Mackall
2007-06-02 19:02 ` Sam Ravnborg
2007-06-02 23:29   ` Christoph Lameter
2007-06-03  8:17     ` Sam Ravnborg

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=20070602104821.d2d8d668.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=clameter@sgi.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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