From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Marcel Holtmann <marcel@holtmann.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the bluetooth tree
Date: Sun, 31 Dec 2017 13:32:18 +0200 [thread overview]
Message-ID: <CAHp75VeLSrkJU0QFQjawn_sfOVhE5_4N68WX1hjenD7ONRz1yw@mail.gmail.com> (raw)
In-Reply-To: <20171230074406.GA26800@x1c.home>
On Sat, Dec 30, 2017 at 9:44 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> Hi,
>
> On Sat, Dec 30, 2017, Stephen Rothwell wrote:
>> On Sat, 30 Dec 2017 10:25:52 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> > Commit
>> >
>> > 0a03f98b98c2 ("Bluetooth: Add a new 04ca:3015 QCA_ROME device")
>> >
>> > is missing a Signed-off-by from its .
>> ^
>> committer
>
> It was me who originally committed and pushed this to the bluetooth-next
> tree, and the commit does have a signed-off-by from me. However, it
> looks like Marcel did some reshuffling/rebasing of the tree and now the
> commit shows him in the committer field.
In PDx86 subsystem we in the result of this check split our (Darren's
and mine) review queues to a separate *non-published* (OK, they are
visible, but not considered published) branches.
Rebase, as stated that time by Linus, as formally creating new commits.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2017-12-31 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 23:25 linux-next: Signed-off-by missing for commit in the bluetooth tree Stephen Rothwell
2017-12-29 23:32 ` Stephen Rothwell
2017-12-30 7:44 ` Johan Hedberg
2017-12-31 11:32 ` Andy Shevchenko [this message]
2020-04-28 22:09 Stephen Rothwell
2021-01-26 8:54 Stephen Rothwell
2021-01-26 9:46 ` Bastien Nocera
2021-04-08 0:00 Stephen Rothwell
2022-07-24 21:57 Stephen Rothwell
2022-07-24 22:17 ` Stephen Rothwell
2022-09-05 21:54 Stephen Rothwell
2022-09-20 22:30 Stephen Rothwell
2023-07-05 23:10 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=CAHp75VeLSrkJU0QFQjawn_sfOVhE5_4N68WX1hjenD7ONRz1yw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).