public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: "George G. Davis" <gdavis@mvista.com>
Cc: Greg KH <greg@kroah.com>, <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	<torvalds@linux-foundation.org>, <stable@kernel.org>,
	<jason.wessel@windriver.com>, Andi Kleen <andi@firstfloor.org>,
	<lwn@lwn.net>
Subject: Re: Announcement: Plans for v2.6.34-longterm
Date: Tue, 8 Nov 2011 18:11:45 -0500	[thread overview]
Message-ID: <4EB9B731.9040804@windriver.com> (raw)
In-Reply-To: <ADA45A9A-E9A4-4B4C-80FF-711340F931BB@mvista.com>

On 11-11-08 05:14 PM, George G. Davis wrote:
> Greetings,
> 

[...]

> 
> Are there any plans to continue maintenance of v2.6.34-longterm now that
> kernel.org is back online?

Yes,  in fact I have a queue ready for review shortly.  However I didn't
want to overtax the kernel.org maintainers with nagging questions about
longterm/stable directory layout & restoration -- as I'm sure they had more
than their hands full with getting people back on the server and getting
stuff functional for the merge window which just closed yesterday.

Paul.

> 
> TIA!
> 
> --
> Regards,
> George

  reply	other threads:[~2011-11-08 23:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 21:07 Announcement: Plans for v2.6.34-longterm Paul Gortmaker
2010-12-04 17:27 ` Greg KH
2010-12-05  0:45   ` Paul Gortmaker
2010-12-04 17:28 ` Greg KH
2010-12-05  1:16   ` Paul Gortmaker
2010-12-05 16:50     ` Greg KH
2010-12-06  4:54       ` Bruce Ashfield
2010-12-06  5:35   ` Minchan Kim
2010-12-06  6:01     ` Minchan Kim
2011-11-08 22:14 ` George G. Davis
2011-11-08 23:11   ` Paul Gortmaker [this message]
2011-11-08 23:52     ` Greg KH
2011-11-09  3:20       ` Paul Gortmaker
2011-11-10 19:54         ` Greg KH
2011-11-10 20:29           ` Paul Gortmaker
2011-11-09 17:12     ` George G. Davis

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=4EB9B731.9040804@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=gdavis@mvista.com \
    --cc=greg@kroah.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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