linux-kernel - Re: [ 00/53] 3.2.18-stable review

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 19 May 2012 00:04:45 +0200
From:	Willy Tarreau <w@....eu>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Greg KH <greg@...ah.com>, Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk
Subject: Re: [ 00/53] 3.2.18-stable review

Hi Ben,

On Fri, May 18, 2012 at 11:00:56PM +0100, Ben Hutchings wrote:
> On Fri, 2012-05-18 at 11:22 -0700, Greg KH wrote:
(...)
> > Ben, care to put the tarball somewhere so I can update it, or should I
> > be poking the kernel.org admins to get you write access to this
> > directory (I think the later would be best...)
> 
> Seems like it might be easier for everyone if I would just send the rc1
> combined patch in email.  Anyway, here it is as an attachment.

I too think that sending rc patches along with the email is better,
especially for longterm branches which tend to see their patch size
drop quickly. In fact it offers more flexibility for sending updates
when something is known to be broken, and I'm really not convinced
at all that anyone downloads the longterm pre-releases without having
received the announcement email !

Just my 2 cents,
Willy

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