From: "Theodore Ts'o" <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jeffrey Merkey <jeffmerkey@gmail.com>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64
Date: Tue, 15 Mar 2016 11:16:18 -0400 [thread overview]
Message-ID: <20160315151618.GQ29218@thunk.org> (raw)
In-Reply-To: <20160315130339.688689bd@canb.auug.org.au>
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
next prev parent reply other threads:[~2016-03-15 15:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 23:50 [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64 Jeffrey Merkey
2016-03-14 23:57 ` Joe Perches
2016-03-15 0:24 ` Stephen Rothwell
2016-03-15 0:40 ` Jeffrey Merkey
2016-03-15 2:03 ` Stephen Rothwell
2016-03-15 15:16 ` Theodore Ts'o [this message]
2016-03-16 23:27 ` Jeffrey Merkey
2016-03-18 5:31 ` Jeffrey Merkey
2016-03-18 5:40 ` Joe Perches
2016-03-18 5:43 ` Jeffrey Merkey
2016-03-25 8:36 ` Ingo Molnar
2016-03-25 17:17 ` Jeffrey Merkey
2016-03-25 17:27 ` Jeffrey Merkey
2016-03-25 23:01 ` Jeffrey Merkey
2016-03-25 23:02 ` Jeffrey Merkey
2016-03-26 1:48 ` Stephen Rothwell
2016-03-26 1:56 ` Jeffrey Merkey
2016-03-26 1:48 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160315151618.GQ29218@thunk.org \
--to=tytso@mit.edu \
--cc=jeffmerkey@gmail.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox