From: Greg KH <greg@kroah.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "George G. Davis" <gdavis@mvista.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 15:52:56 -0800 [thread overview]
Message-ID: <20111108235256.GB9866@kroah.com> (raw)
In-Reply-To: <4EB9B731.9040804@windriver.com>
On Tue, Nov 08, 2011 at 06:11:45PM -0500, Paul Gortmaker wrote:
> 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.
Ah, I'll handle this :)
So, in talking with Andi, we decided that I would just keep the "main"
linux-stable.git tree on kernel.org. When you do a new release, I'll
merge that into the linux-stable.git tree and do the "official" tarball
release with the proper stable kernel signing key.
This should make your life a whole lot easier, just clone the existing
linux-stable.git tree, add your releases to the proper branch, and do a
pull request to me when you have it all ready to go.
It also makes managing things on the kernel.org side easier with
permissions and the like, as sharing a git tree can get messy as we've
seen in the past.
Sound reasonable?
Also, I would like to populate the linux-stable.git tree with the
missing .34-longterm releases that you have already done, care to
provide a git tree that I can pull from for those now?
Oh, you will need a kernel.org account for this, but I'm assuming that
you already have that set up, right? If not, please do that first and
if you have any problems with it, let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2011-11-08 23:53 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
2011-11-08 23:52 ` Greg KH [this message]
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=20111108235256.GB9866@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=gdavis@mvista.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=paul.gortmaker@windriver.com \
--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