linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Lameter <cl@linux-foundation.org>
Subject: Re: linux-next: reminder
Date: Wed, 10 Jul 2013 09:44:58 +0300	[thread overview]
Message-ID: <51DD02EA.9010909@kernel.org> (raw)
In-Reply-To: <20130710100707.d79b5df2a826faf1caecf3b4@canb.auug.org.au>

On 07/10/2013 03:07 AM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 2 Jul 2013 17:09:57 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> We are in the merge window, so please do not add anything to your
>> linux-next included branches that is not destined for v3.11 until after
>> v3.11-rc1 is released.
>
> No, really :-(
>
> i.e. maintainers should be saying "No" to any "features" that were not
> ready before the merge window opened (even when the maintainer and the
> developer are the same person) ...

It's being queued for v3.11. I was on vacation for two weeks
with no internet at the worst possible moment and I was backlogged
with slab patches.

Sorry for breaking things!

			Pekka

  reply	other threads:[~2013-07-10  6:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02  7:09 linux-next: reminder Stephen Rothwell
2013-07-10  0:07 ` Stephen Rothwell
2013-07-10  6:44   ` Pekka Enberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-29 21:59 Stephen Rothwell
2014-10-07 22:57 Stephen Rothwell
2013-11-07 23:25 Stephen Rothwell
2012-12-12 20:46 Stephen Rothwell
2010-02-28 23:35 Stephen Rothwell

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=51DD02EA.9010909@kernel.org \
    --to=penberg@kernel.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).