From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Patch reminder
Date: Mon, 16 Nov 2009 15:01:59 +0100 [thread overview]
Message-ID: <20091116140159.GB11434@linux-mips.org> (raw)
Folks,
We're now at 2.6.32-rc7 so not far away from a 2.6.32 release. Linus wants
us maintainers to stop accepting non-bugfix patches for next release after
that (which would be 2.6.33) around rc5.
Which has already passed by, so I should stop accepting new stuff for
2.6.33 already. Year long experience is I tend to get flooded with
patches by the time a final release is out. That's actually the time by
which I should send everything I've collected in the queue tree to Linus
so a terrible point to merge yet more stuff.
Anyway, I want this message to be the last call for any sort of feature
or other instrusive patches you folks may have hidden up in your sleeve
for 2.6.33.
"Post 'en now or forever hold your peace" ;-)
Ralf
reply other threads:[~2009-11-16 14:01 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=20091116140159.GB11434@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.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).