From: Len Brown <lenb@kernel.org>
To: Linux-acpi@vger.kernel.org
Subject: linux kernel release cycle
Date: Wed, 12 Sep 2007 23:12:18 -0400 [thread overview]
Message-ID: <200709122312.18542.lenb@kernel.org> (raw)
At the kernel summit, Linus made it quite clear that
he wants almost all changes from sub-system trees (like ACPI)
in the beginning of the 2-week merge window -- preferably the 1st day.
He wants no-function-change cleanups to happen in the merge window too,
though I got the impression that later in the merge window was acceptable for those,
unless your name is Andrew Morton who can push those in rc2.
After rc1 is declared, we should be pushing upstream nothing but bug fixes --
with the focus on regression bug fixes.
This means that if you want to push any feature-related patches
in 2.6.24, I basically need them in my test tree now -- 2.6.23-rc6.
thanks,
-Len
reply other threads:[~2007-09-13 3:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200709122312.18542.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=Linux-acpi@vger.kernel.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).