public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Linux v2.6.27-rc1
Date: Tue, 29 Jul 2008 10:31:31 -0700	[thread overview]
Message-ID: <adafxps4mx8.fsf@cisco.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807290945030.3334@nehalem.linux-foundation.org> (Linus Torvalds's message of "Tue, 29 Jul 2008 09:59:18 -0700 (PDT)")

 >    That may not sound like much, but it's enough to make me worry about 
 >    'next'. I worry that 'it has been in next' has become a code-word for 
 >    "pull this, because it's good", and I'm not at all convinced that 
 >    'next' sees any real critical checking.

I've been mentioning that my trees have been in next as code for, "I
don't think this should break the build or clash too badly with anything
else."  And next has been useful to me on several occasions for catching
that sort of problem before things hit mainline.

 - R.

  reply	other threads:[~2008-07-29 17:31 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  3:23 Linux v2.6.27-rc1 Linus Torvalds
2008-07-29  4:01 ` Nick Piggin
2008-07-29  9:49 ` 2.6.27-rc1: zd1211rw association fails Alistair John Strachan
2008-07-29 10:09   ` Johannes Berg
2008-07-29 11:25     ` Alistair John Strachan
2008-07-29 11:26       ` Johannes Berg
2008-07-29 11:37         ` Hugh Dickins
2008-07-29 11:46         ` Kalle Valo
2008-07-29 11:55         ` Alistair John Strachan
2008-07-29 12:04     ` Theodore Tso
2008-07-29 12:09       ` Johannes Berg
2008-07-29 12:15         ` Johannes Berg
2008-07-29 15:18           ` Theodore Tso
2008-07-29 17:52           ` John W. Linville
2008-07-30  4:48             ` David Miller
2008-07-29 13:57 ` Oops in microcode sysfs registration, Alistair John Strachan
2008-07-29 16:22   ` Pekka Paalanen
2008-07-29 16:50     ` Alistair John Strachan
2008-07-30  9:07       ` Dmitry Adamushko
2008-07-30 10:35         ` Dmitry Adamushko
2008-07-30 13:28           ` Peter Oruba
2008-07-31 12:49           ` Alistair John Strachan
2008-07-31 16:56           ` Ingo Molnar
2008-07-31 19:52             ` Dmitry Adamushko
2008-07-31 19:55               ` Dmitry Adamushko
2008-07-29 16:27 ` Linux v2.6.27-rc1 Jesse Barnes
2008-07-29 16:59   ` Linus Torvalds
2008-07-29 17:31     ` Roland Dreier [this message]
2008-07-30  9:03     ` Andrew Morton
2008-07-31 22:22       ` Linux v2.6.27-rc1: linux-next Rafael J. Wysocki
2008-07-29 20:49 ` Linux v2.6.27-rc1: problem with firmware stuff Rafael J. Wysocki
2008-07-29 21:01   ` Rafael J. Wysocki
2008-07-29 21:01     ` Linus Torvalds
2008-07-29 22:26       ` David Woodhouse
2008-07-29 21:37 ` Linux v2.6.27-rc1 Sam Ravnborg
2008-07-29 21:42   ` Linus Torvalds
2008-07-29 21:59     ` Sam Ravnborg
2008-07-29 22:03       ` Linus Torvalds
2008-07-29 22:30         ` Sam Ravnborg
2008-07-29 22:03 ` Linux v2.6.27-rc1: fails to compile Grant Coady
2008-07-29 22:40   ` Frederik Deweerdt
2008-07-29 23:46     ` Grant Coady
  -- strict thread matches above, loose matches on Subject: below --
2008-07-29 11:23 Linux v2.6.27-rc1 Martin Knoblauch
2008-07-29 11:57 ` Peter Zijlstra
2008-07-29 12:08 Martin Knoblauch

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=adafxps4mx8.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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