From: Greg KH <greg@kroah.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Bryan Wu <bryan.wu@analog.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org,
Nish Aravamudan <nish.aravamudan@gmail.com>
Subject: Re: Linux 2.6.22.1
Date: Fri, 13 Jul 2007 12:52:21 -0700 [thread overview]
Message-ID: <20070713195221.GC20092@kroah.com> (raw)
In-Reply-To: <20070713064751.GA3492@stusta.de>
On Fri, Jul 13, 2007 at 08:47:51AM +0200, Adrian Bunk wrote:
> On Thu, Jul 12, 2007 at 11:16:17PM -0700, Greg KH wrote:
> > On Fri, Jul 13, 2007 at 02:16:20PM +0800, Bryan Wu wrote:
> > > On Fri, 2007-07-13 at 02:35 +0800, 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?
> > > >
> > >
> > > Could you please open http:// git-pull? I was blocked by company's
> > > firewall except http method -:((.
> >
> > That is up to the kernel.org admins, but last time I checked, I think it
> > was enabled already. Can you pull anything else from kernel.org with
> > http but not this tree?
>
> I found the problem and (ab)used my kstable group rights to fix it:
>
> objects/info/alternates of linux-2.6.22.y.git contained
> /home/ftp/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/objects
> instead of
> /pub/scm/linux/kernel/git/torvalds/linux-2.6.git/objects
>
> This seems to exist on git.kernel.org but not on www.kernel.org,
> explaining why the http method didn't work.
Odd, thanks for fixing that, it was "interesting" to create that tree
and it took me a few tries as I forgot to clone it right when Linus
released so I had to reset the HEAD back to the v2.6.22 release
changeset.
thanks,
greg k-h
next prev parent reply other threads:[~2007-07-13 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 20:06 Linux 2.6.22.1 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
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 [this message]
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=20070713195221.GC20092@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.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 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.