All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: USB tree now closed for 3.11
Date: Tue, 25 Jun 2013 08:25:10 -0700	[thread overview]
Message-ID: <20130625152510.GA20552@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1306251119100.1340-100000@iolanthe.rowland.org>

On Tue, Jun 25, 2013 at 11:21:43AM -0400, Alan Stern wrote:
> On Tue, 25 Jun 2013, Greg KH wrote:
> 
> > Hi all,
> > 
> > With the release of the 3.10-rc7 kernel, I think it's time to close the
> > USB tree for new features / cleanups for 3.11.  So I'm closing my
> > tree, and will only be applying obvious bugfixes or regressions to it
> > until 3.11-rc1 comes out.
> > 
> > You can keep sending me patches for the tree that don't fit the "bugfix"
> > category, but note that I'll be storing them away to wait for 3.11-rc1
> > comes out, which might be a few weeks, so please be patient.
> > 
> > The USB tree right now contains 382 patches, and the diffstat
> > summary is:
> > 	 410 files changed, 18183 insertions(+), 4956 deletions(-)
> 
> Instead of storing away new patches where people can't easily get at
> them, you could create a temporary branch to hold them until 3.11-rc1
> is released.  Would that involve a significant amount of extra work?

Yes that would, because I'm busy doing other merge-related things for
these next 3 weeks, I don't have the time to be building a new tree.  I
supposed you could always use patchwork to see the pending patches, but
I need this time "away" from applying patches to catch up on my other
tasks.

sorry,

greg k-h

      reply	other threads:[~2013-06-25 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 15:07 USB tree now closed for 3.11 Greg KH
2013-06-25 15:21 ` Alan Stern
2013-06-25 15:25   ` Greg KH [this message]

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=20130625152510.GA20552@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.