From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: 2.6.22 fixes and 2.6.23 patches
Date: Thu, 31 May 2007 17:43:42 +0100 [thread overview]
Message-ID: <20070531164342.GA13399@linux-mips.org> (raw)
In the past there was a strong tendence that people were sending me patches
for 2.6.$(n + 1) only after 2.6.n was released. That's a bit painful for
me as it leaves me only the merge window to sort out all the dependencies
and issues that may arise from those patches and oh yes, sometimes my
employer wants me something else to do in the same time. So if you have
patches pending, send them in time. I can always drop stuff for $(n + 1)
in the -queue tree even when we're in deep freeze. Think of it as the
Linux/MIPS -mm tree.
Also it's high time to get all fixes for 2.6.22 upstream so if you have
something send it ASAP, if you think I may have lost it send again.
Thanks,
Ralf
reply other threads:[~2007-05-31 16:43 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=20070531164342.GA13399@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