From: Greg KH <gregkh@linuxfoundation.org>
To: devel@driverdev.osuosl.org, linux-usb@vger.kernel.org,
linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: USB, TTY, char/misc, and Staging trees now closed for 3.13
Date: Wed, 30 Oct 2013 10:29:04 -0700 [thread overview]
Message-ID: <20131030172904.GA11800@kroah.com> (raw)
Hi all,
Given that 3.12 will be out in a few days, it's time to close my trees
for new patches until 3.13-rc1 is out.
The merge window for 3.13-rc1 is going to be a bit longer than normal as
Linus has pointed out, due to travel and conferences. I'll also be
traveling for 2 weeks, so my response time to patches is going to be
_hugely_ delayed.
So much delayed, that I would _really_ appreciate people not sending
patches until 3.13-rc1 is out, just so that I can not have a ton of
pending patches to dig through when that happens. If patches are sent
before 3.13-rc1 is out, I will queue them up, but note that it will be
delayed.
Due to travel, conferences, and other stuff I want to work on (i.e.
stable releases and xen kexec work), my response time to email is going
to be really slow for a few weeks.
thanks,
greg k-h
reply other threads:[~2013-10-30 17:29 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=20131030172904.GA11800@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@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 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.