From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [GIT PULL] [3.2] Please pull tegra boards for 3.2
Date: Fri, 26 Aug 2011 09:32:52 +0100 [thread overview]
Message-ID: <20110826083252.GE11250@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMj5P9yLO0My4UB7AEj+9NdmYq8HYwVMd3Uv1NQO6+WP7A@mail.gmail.com>
On Thu, Aug 25, 2011 at 10:23:21PM -0700, Olof Johansson wrote:
> Ok. Sounds like there might be some use for a temporary "work in
> progress" branch for linux-next for patches that are nearly ready to
> go but not quite that needs air time, but not really for anything
> beyond that.
Bad idea.
linux-next's policy is that everything in linux-next should be ready
for mainline - not nearly ready.
Linus is threatening at the next merge window to ignore pull requests
from maintainers, and just pull the entire linux-next tree into his at
the beginning. Anything in linux-next which is "work in progress" will
therefore find its way immediately into mainline in whatever state it's
in.
So, everyone needs to ensure that linux-next only contains code that's
100% ready for merging during the next merge window. Everything else
should not be in linux-next.
next prev parent reply other threads:[~2011-08-26 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 7:35 [GIT PULL] [3.2] Please pull tegra boards for 3.2 Olof Johansson
[not found] ` <CAOesGMhFi0fsVdTe0ThhF636tqUhiWk7oZ41QKmL4dd3TcQ4_g@mail.gmail.com>
2011-08-16 14:48 ` Fwd: " Arnd Bergmann
2011-08-16 15:03 ` Nicolas Pitre
2011-08-16 15:27 ` Thomas Gleixner
2011-08-16 19:30 ` Olof Johansson
2011-08-16 21:12 ` Arnd Bergmann
2011-08-26 5:23 ` Olof Johansson
2011-08-26 8:32 ` Russell King - ARM Linux [this message]
2011-08-26 9:15 ` Sascha Hauer
2011-08-26 5:40 ` Olof Johansson
2011-08-26 15:53 ` Arnd Bergmann
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=20110826083252.GE11250@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).