All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [ANNOUNCE] Linux 2.6.35.10 has been released
Date: Sat, 18 Dec 2010 16:21:46 -0800	[thread overview]
Message-ID: <20101219002146.GA11568@kroah.com> (raw)
In-Reply-To: <877hf66929.fsf@depni.sinp.msu.ru>

On Sat, Dec 18, 2010 at 09:54:38PM +0000, Serge Belyshev wrote:
> Andi Kleen <andi@firstfloor.org> writes:
> 
> > A new longterm 2.6.35.10 kernel has been released. This release contains security
> > fixes and all 2.6.35 users are encouraged to update. This continues
> > the 2.6.35 stable series under a new name.
> 
> Could you please update this tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.35.y.git ?

No, the "stable" trees are not being updated anymore, they have moved to
the longterm git directory instead.

> This, and all other stable trees are mirrored here:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6-stable.git
> it would be nice to keep it up-to-date.

That tree is automatically generated by some scripts on kernel.org,
which might need to be tweaked to handle the movement of the trees now.

thanks,

greg k-h

  reply	other threads:[~2010-12-19  0:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 23:27 [ANNOUNCE] Linux 2.6.35.10 has been released Andi Kleen
2010-12-15 10:00 ` Mario 'BitKoenig' Holbe
2010-12-18 21:54 ` Serge Belyshev
2010-12-19  0:21   ` Greg KH [this message]
2010-12-19 10:36     ` [stable] " Andi Kleen
2010-12-19 16:39       ` Greg KH
2010-12-19 16:56         ` Willy Tarreau
2010-12-19 18:43           ` david
2010-12-19 17:48         ` Andi Kleen

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=20101219002146.GA11568@kroah.com \
    --to=greg@kroah.com \
    --cc=andi@firstfloor.org \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.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.