linux-kernel - Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86

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:	Wed, 16 Mar 2016 17:27:49 -0600
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Jeffrey Merkey <jeffmerkey@...il.com>,
	Joe Perches <joe@...ches.com>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/15/16, Theodore Ts'o <tytso@....edu> wrote:
> On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote:
>> We don't generally PGP (GPG) sign commits in the kernel tree (so "-S"
>> is not required), just tags.  However we always require that anyone who
>> handles a patch adds a Signed-off-by line to the final commit.  See
>> Documentation/SubmittingPatches Section 11.
>
> In general all commits should have a Signed-Off-By line added.  Once
> the git branch gets merged, it's hard to tell what is the final commit
> and what isn't, and in general different commits will have different
> people needing to vouch for the origins for the contents of that commit.
>
> Cheers,
>
> 							- Ted
> 							
>

Hi Ted,

I will repost this pull request with a signed-off by line for Linus to
consider.    I am not certain who all should be included in the review
and I have to be careful how many email recipients I copy.   I will
post to the folks Joe Perches copied.

Jeff