From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Linux 3.2 merge window
Date: Wed, 19 Oct 2011 22:51:56 +0300 [thread overview]
Message-ID: <1319053918.5227.2.camel@koala> (raw)
In-Reply-To: <CAN8TOE84X+rDQuVfP5O-XZduiQ38EWyn=dPhYfYa2EB4squCJw@mail.gmail.com>
Let's pt David to "To:"
On Wed, 2011-10-19 at 10:44 -0700, Brian Norris wrote:
> I see that mainline has entered 3.1-rc10 with a notice from Linus that
> 3.1 should be released soon and he'd be moving on to the 3.2 merge
> window. Any idea if dwmw will get around to merging l2-mtd-2.6?
> Sometime next year we'll be basing a new kernel on the current 3.x,
> and I'd appreciate having the last several months' work merged in the
> next release.
Yeah, last merge window was missed. I chatted with David an he said that
he will not miss this one. Besides, I will try to grab him in the kernel
summit and remind (going to happen next Monday) :-)
Artem.
next prev parent reply other threads:[~2011-10-19 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 17:44 Linux 3.2 merge window Brian Norris
2011-10-19 19:51 ` Artem Bityutskiy [this message]
2011-11-07 21:23 ` Artem Bityutskiy
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=1319053918.5227.2.camel@koala \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@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