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]

Message-ID: <20160315151618.GQ29218@thunk.org>
Date:	Tue, 15 Mar 2016 11:16:18 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	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 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