From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Radim Krčmář" <rkrcmar@redhat•com>
Cc: David Hildenbrand <david@redhat•com>,
Marcelo Tosatti <mtosatti@redhat•com>,
Gleb Natapov <gleb@kernel•org>, KVM <kvm@vger•kernel.org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Paolo Bonzini <pbonzini@redhat•com>
Subject: Re: linux-next: Signed-off-by missing for commit in the kvm tree
Date: Sat, 12 Aug 2017 00:01:46 +1000 [thread overview]
Message-ID: <20170812000146.0d133ee6@canb.auug.org.au> (raw)
In-Reply-To: <20170811123623.GA28649@flask>
Hi Radim,
On Fri, 11 Aug 2017 14:36:24 +0200 Radim Krčmář <rkrcmar@redhat•com> wrote:
>
> Should all rebases be done with the --signoff option?
More or less. rebase with the --signoff option will add a duplicate
Signed-off-by unless the already existing one is last in the current
commit.
Linus has said that doing a rebase is no different to applying a patch,
so a new committer needs to add a Signed-off-by tag.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-08-11 14:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 23:28 linux-next: Signed-off-by missing for commit in the kvm tree Stephen Rothwell
2017-08-11 6:29 ` David Hildenbrand
2017-08-11 12:36 ` Radim Krčmář
2017-08-11 14:01 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-06 21:39 Stephen Rothwell
2018-08-06 21:55 ` Paolo Bonzini
2018-12-21 13:57 Stephen Rothwell
2020-01-23 20:43 Stephen Rothwell
2020-04-19 22:26 Stephen Rothwell
2020-04-20 22:32 Stephen Rothwell
2020-06-11 1:04 Stephen Rothwell
2020-08-04 22:29 Stephen Rothwell
2021-02-04 20:18 Stephen Rothwell
2021-02-05 14:36 ` Joao Martins
2021-09-30 22:42 Stephen Rothwell
2021-12-16 18:52 Stephen Rothwell
2022-01-08 7:24 Stephen Rothwell
2022-03-21 13:07 Stephen Rothwell
2022-05-22 0:51 Stephen Rothwell
2022-05-23 22:33 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=20170812000146.0d133ee6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=david@redhat$(echo .)com \
--cc=gleb@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mtosatti@redhat$(echo .)com \
--cc=pbonzini@redhat$(echo .)com \
--cc=rkrcmar@redhat$(echo .)com \
/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