All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Greg KH <greg@kroah.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Serge Belyshev <belyshev@depni.sinp.msu.ru>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [ANNOUNCE] Linux 2.6.35.10 has been released
Date: Sun, 19 Dec 2010 17:56:53 +0100	[thread overview]
Message-ID: <20101219165653.GK26410@1wt.eu> (raw)
In-Reply-To: <20101219163935.GA23359@kroah.com>

On Sun, Dec 19, 2010 at 08:39:35AM -0800, Greg KH wrote:
> On Sun, Dec 19, 2010 at 11:36:10AM +0100, Andi Kleen wrote:
> > On Sat, Dec 18, 2010 at 04:21:46PM -0800, Greg KH wrote:
> > > > 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.
> > 
> > It would be good if the old stable git tree for 2.6.35 was deleted to avoid
> > confusion. Greg, what do you think?
> 
> No, we have never deleted any of the other trees when we "stopped"
> maintaining them, so we shouldn't delete these either.
> 
> I need to look this week at using git notes to mark trees as unsupported
> or supported in a way that will work well.  That should solve this issue
> as the note could also say 'go look at the longterm kernel' as well.

Once again, I think it's not too late to replace the old trees with a
symlink to the new one (or the opposite), considering that users have
not updated their scripts yet. Also I'm realizing it's a bit bothering
as a user to have to change the address of the remote when tracking such
a branch.

Regards,
Willy


  reply	other threads:[~2010-12-19 16:57 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   ` [stable] " Greg KH
2010-12-19 10:36     ` Andi Kleen
2010-12-19 16:39       ` Greg KH
2010-12-19 16:56         ` Willy Tarreau [this message]
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=20101219165653.GK26410@1wt.eu \
    --to=w@1wt.eu \
    --cc=andi@firstfloor.org \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=greg@kroah.com \
    --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.