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, 24 Apr 2010 11:30:16 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	tytso@....edu
CC:	Greg Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Documentation: -stable rules: upstream commit ID
 requirement reworded

Stefan Richter wrote:
> tytso@....edu wrote:
>> I find the upstream commit ID to be highly useful when looking at
>> commits in the stable tree.  So it would be nice IMHO if we could
>> enforce this requirement regardless of whether the submission path is
>> via e-mail or git.
...
> Apparently Greg's scripts modify the
> changelogs respectively when he cherry-picks from linux-2.6.git, so the
> requirement is also always fulfilled with this alternative submission path.

Or do you mean submission directly from a developer's git tree to stable
via git pull by Greg?  Is this been done?  If yes, I suppose this comes
only from people who know very well how a stable patch is meant to look
like.  Nevertheless I could send another adjustment for
Documentation/stable_kernel_rules.txt if this is another actual
submission path.
-- 
Stefan Richter
-=====-==-=- -=-- ==---
http://arcgraph.de/sr/
--
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