From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Masami Hiramatsu <mhiramat@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the ftrace tree
Date: Tue, 13 Dec 2022 11:42:49 +1100 [thread overview]
Message-ID: <20221213114249.1bac79ce@canb.auug.org.au> (raw)
In-Reply-To: <20221212175642.77cba577@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Hi Steven,
On Mon, 12 Dec 2022 17:56:42 -0500 Steven Rostedt <rostedt@goodmis•org> wrote:
>
> Bah, not sure how this happened. I thought I pulled these patches directly
> from Masami. Does a rebase change the committer tags? As I probably rebased
> them on top of my branch.
From "git help rebase"
--signoff
Add a Signed-off-by trailer to all the rebased commits. Note that
if --interactive is given then only commits marked to be picked,
edited or reworded will have the trailer added.
So this is not done by default. Yet another reason to avoid rebasing
others work unless absolutely necessary.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-13 0:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 21:52 linux-next: Signed-off-by missing for commit in the ftrace tree Stephen Rothwell
2022-12-12 22:56 ` Steven Rostedt
2022-12-13 0:42 ` Stephen Rothwell [this message]
2022-12-13 1:11 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 21:28 Stephen Rothwell
2024-09-20 14:19 ` Steven Rostedt
2023-06-22 22:35 Stephen Rothwell
2023-06-22 22:48 ` Steven Rostedt
2023-06-23 8:36 ` Masami Hiramatsu
2023-02-12 21:17 Stephen Rothwell
2023-02-13 0:35 ` Steven Rostedt
2023-02-13 12:33 ` Masami Hiramatsu
2021-10-26 21:17 Stephen Rothwell
2021-10-26 21:22 ` Steven Rostedt
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=20221213114249.1bac79ce@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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