From: Greg KH <greg@kroah.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Stefan Roese <stefan.roese@gmail.com>,
Mathias Krause <minipli@googlemail.com>,
Chris Wright <chrisw@sous-sol.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-2.6-stable.git abandoned?
Date: Mon, 20 Sep 2010 07:41:26 -0700 [thread overview]
Message-ID: <20100920144126.GC24083@kroah.com> (raw)
In-Reply-To: <20100920135257.GB5349@kryptos.osrc.amd.com>
On Mon, Sep 20, 2010 at 03:52:57PM +0200, Borislav Petkov wrote:
> From: Jonathan Corbet <corbet@lwn.net>
> Date: Mon, Sep 20, 2010 at 07:38:06AM -0600
>
> > On Mon, 20 Sep 2010 15:35:08 +0200
> > Stefan Roese <stefan.roese@gmail.com> wrote:
> >
> > > Hmmm, looking at:
> > >
> > > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=summary
> > >
> > > The last change went 3 weeks ago into this git repository.
> >
> > Try:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.34.y.git
> >
> > if you want 2.6.34 updates.
>
> Actually, I use the first repo above for stable updates too because it
> conveniently contains all 2.6.3x releases. Isn't that one the official
> combined repo for stable updates? Can we have some clarification from
> the -stable team on which repo we should take?
The "combined" tree is automagically generated by some script on
kernel.org and I have no control over it at all, sorry. If it's not
working properly, poke the kernel.org admins.
I use the individual kernel trees for all of the "development" of the
stable releases, so you can be sure that those work as they are the ones
needed to generate the release.
hope this helps,
greg k-h
prev parent reply other threads:[~2010-09-20 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 6:30 linux-2.6-stable.git abandoned? Mathias Krause
2010-09-20 7:39 ` Pekka Enberg
2010-09-20 13:18 ` Jonathan Corbet
2010-09-20 13:35 ` Stefan Roese
2010-09-20 13:38 ` Jonathan Corbet
2010-09-20 13:52 ` Borislav Petkov
2010-09-20 14:41 ` 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=20100920144126.GC24083@kroah.com \
--to=greg@kroah.com \
--cc=bp@amd64.org \
--cc=chrisw@sous-sol.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=stefan.roese@gmail.com \
/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.