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]
Message-ID: <20121201005225.GA19767@kroah.com>
Date:	Fri, 30 Nov 2012 16:52:25 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Anthony Foiani <tkil@...ye.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: Enumerate the guidelines for stable
 patches.

On Fri, Nov 30, 2012 at 05:44:13PM -0700, Anthony Foiani wrote:
> 
> From: Anthony Foiani <anthony.foiani@...il.com>
> 
> Having recently received a formletter rejection on a stable patch, I
> found it difficult to determine exactly which guideline I had missed.
> 
> Numbering the guidelines will allow the stable maintainer to quickly
> and easily indicate which guidelines have not been followed.
> 
> The actual changes are only the addition of clause numbering, and the
> wishful thinking added to S15.

Is this really needed?  For the large majority of the stable patches,
specifically enumerating this isn't a big deal, it's a tiny patch, and
if you think I'll remember to tell you which specific clause you didn't
follow, then you think I have more spare time than I really do.

Sorry, but no, I don't think this patch is ok, especially that S15
clause, nice try :)

greg k-h
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ