From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: Linux 3.3-1 out - merge window closed
Date: Fri, 20 Jan 2012 12:41:43 -0500 [thread overview]
Message-ID: <20120120174143.GA15673@home.goodmis.org> (raw)
In-Reply-To: <20120120151452.2fe57bb87218f575e8909caf@canb.auug.org.au>
On Fri, Jan 20, 2012 at 03:14:52PM +1100, Stephen Rothwell wrote:
>
> This leaves 1174 commits (13%) in v3.3-rc1 that were not in next-20120106
> for some reason (not too bad really, I guess). Some will clearly be bug
> fixes, of course. Some will be quilt trees (probably rebased before
> being sent to Linus). Some will be patches that depend on work by others.
Well, 19 of those were ktest patches. Although it's not something we
need to worry about, as it's just a script for users to test their
kernels and not something that would conflict with others. I'll send out
that email to get ktest included into linux-next regardless.
Thanks!
-- Steve
next prev parent reply other threads:[~2012-01-20 17:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 23:58 Linux 3.3-1 out - merge window closed Linus Torvalds
2012-01-20 4:14 ` Stephen Rothwell
2012-01-20 17:41 ` Steven Rostedt [this message]
2012-01-20 20:15 ` Junio C Hamano
2012-01-22 10:35 ` Geert Uytterhoeven
2012-01-26 9:48 ` Andrew Morton
2012-01-23 9:17 ` Ohad Ben-Cohen
2012-01-23 13:18 ` Grant Likely
2012-01-23 15:18 ` Arnd Bergmann
2012-01-24 0:32 ` Rusty Russell
2012-01-31 16:56 ` Paolo Bonzini
2012-02-01 2:49 ` Rusty Russell
2012-02-01 6:47 ` Ohad Ben-Cohen
2012-01-23 15:06 ` Carlos Chinea
2012-01-23 19:43 ` Linus Walleij
2012-01-24 18:57 ` Carlos Chinea
2012-01-25 11:35 ` Artem Bityutskiy
2012-01-25 11:47 ` Pekka Enberg
2012-01-25 12:06 ` 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=20120120174143.GA15673@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.