From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [stable] Linux 2.6.22.1
Date: Thu, 12 Jul 2007 11:46:15 -0700 [thread overview]
Message-ID: <29495f1d0707121146k7b3a7175l1fcb40877e59cfaf@mail.gmail.com> (raw)
In-Reply-To: <20070712184106.GA22849@kroah.com>
On 7/12/07, Greg KH <greg@kroah.com> wrote:
> On Thu, Jul 12, 2007 at 11:35:41AM -0700, Nish Aravamudan wrote:
> > On 7/10/07, Greg KH <greg@kroah.com> wrote:
> > > We (the -stable team) are announcing the release of the 2.6.22.1 kernel.
> > > It contains a security fix for SCTP that somehow forgot to be added to
> > > the 2.6.22 kernel (was already released in the 2.6.21.y releases).
> > > Thanks to Patrick McHardy for noticing the mistake.
> > >
> > > I'll also be replying to this message with a copy of the patch between
> > > 2.6.22 and 2.6.22.1
> > >
> > > The updated 2.6.22.y git tree can be found at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.22.y.git
> >
> > Can you please also update
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6-stable.git
> >
> > ? Maybe make that update part of whatever process you use to push out
> > the 2.6.Y trees, as I've had to ask for this more than once now?
>
> That is a tree that Chris did, and I didn't realize we were maintaining
> it as the "official" stable tree, that is why it is not mentioned in the
> release notes :)
Fair enough -- it's just a little bit easier from my side for
mirroring to only have to mirror one tree rather simply rather than
pulling multiple trees into one (and thus having to add to the list as
time goes on).
> I'll let Chris decide if he wishes to maintain it or not, Chris?
Thanks,
Nish
next prev parent reply other threads:[~2007-07-12 18:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 20:06 Greg KH
2007-07-10 20:06 ` Greg KH
2007-07-12 18:35 ` Nish Aravamudan
2007-07-12 18:41 ` [stable] " Greg KH
2007-07-12 18:46 ` Nish Aravamudan [this message]
2007-07-12 18:52 ` Chris Wright
2007-07-12 19:08 ` Nish Aravamudan
2007-07-12 23:02 ` Domenico Andreoli
2007-07-12 23:03 ` Rene Herman
2007-07-13 6:16 ` Bryan Wu
2007-07-13 6:16 ` Greg KH
2007-07-13 6:28 ` Bryan Wu
2007-07-13 6:34 ` Linus Torvalds
2007-07-13 6:51 ` Chris Wright
2007-07-13 6:58 ` Bryan Wu
2007-07-13 6:47 ` Adrian Bunk
2007-07-13 19:52 ` Greg KH
2007-07-14 0:44 ` H. Peter Anvin
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=29495f1d0707121146k7b3a7175l1fcb40877e59cfaf@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®