linux-kernel - Re: [PATCH 1/3] Documentation: -stable rules: upstream commit ID requirement reworded

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] [day] [month] [year] [list]

Date:	Sat, 24 Apr 2010 12:50:28 -0400
From:	Theodore Tso <tytso@....EDU>
To:	Greg KH <gregkh@...e.de>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Documentation: -stable rules: upstream commit ID requirement reworded


On Apr 24, 2010, at 11:02 AM, Greg KH wrote:
>> 
>>> 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.
> 
> No, it's not a real submission patch, and yes, I always require a git
> commit id in the patch.  If I don't have it, it is explained in the
> patch why it is not in Linus's tree.
> 
> Don't worry, I think the current wording is fine.

Thanks for clarifying, I didn't realize the wording was referring to the cc: stable@ path, where the stable team adds the commit id reference themselves once it's available.   

-- Ted


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