linux-kernel - Re: [stable] [ANNOUNCE] Linux 2.6.35.10 has been released

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1012191040410.16878@asgard.lang.hm>
Date:	Sun, 19 Dec 2010 10:43:40 -0800 (PST)
From:	david@...g.hm
To:	Willy Tarreau <w@....eu>
cc:	Greg KH <greg@...ah.com>, Andi Kleen <andi@...stfloor.org>,
	Serge Belyshev <belyshev@...ni.sinp.msu.ru>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [stable] [ANNOUNCE] Linux 2.6.35.10 has been released

On Sun, 19 Dec 2010, Willy Tarreau wrote:

> 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.

the bigger problem is realizing that you need to change the remote.

the old way, all the stable kernels were togeather, and new ones (of any 
branch) would show up whenever they were released.

if we (the users) now have to setup a different remote for each person who 
manages a tree, things are getting significantly more complex (and more 
fragmented)

If there is any way that all the stable and long term trees can be kept 
under the -stable location it would be great.

the next best would be to have a -longterm like stable. But if that can be 
done, it should be pretty easy to then combine it with -stable as well, 
and _far_ more convienient for the users.

David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/