From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 jc_docs tree
Date: Thu, 10 May 2018 15:44:08 -0600 [thread overview]
Message-ID: <20180510154359.4aea2351@lwn.net> (raw)
In-Reply-To: <20180511074049.26072ec8@canb.auug.org.au>
On Fri, 11 May 2018 07:40:49 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Commit
>
> 5a779c40a8ad ("Revert "Documentation/features/vm: Remove arch support status file for 'pte_special'"")
>
> is missing a Signed-off-by from its author and committer. Reverts are
> commits too. ;-)
Argh. I'm really not having a good time with this.
I've rebase-fixed it, I doubt anybody (except you! :) has pulled my tree
in the half-hour it was there...apologies if I'm wrong.
Thanks,
jon
next prev parent reply other threads:[~2018-05-10 21:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 21:40 linux-next: Signed-off-by missing for commit in the jc_docs tree Stephen Rothwell
2018-05-10 21:44 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-26 22:01 Stephen Rothwell
2019-06-26 22:09 ` Jonathan Corbet
2020-05-25 22:01 Stephen Rothwell
2020-05-26 14:44 ` Jonathan Corbet
2020-06-05 20:28 ` Alexander A. Klimov
2020-06-05 20:34 ` Jonathan Corbet
2020-08-24 23:13 Stephen Rothwell
2020-08-24 23:18 ` Jonathan Corbet
2020-10-21 21:55 Stephen Rothwell
2020-10-21 22:19 ` Jonathan Corbet
2020-10-22 6:55 ` Zheng, Fam
2023-01-19 21:34 Stephen Rothwell
2023-01-19 21:48 ` Jonathan Corbet
2023-01-19 21:59 ` Jakob Koschel
2024-01-04 6:11 Stephen Rothwell
2025-06-09 22:17 Stephen Rothwell
2025-06-09 22:23 ` Jonathan Corbet
2025-06-16 2:19 ` liu shouye
2025-06-19 19:24 ` Jonathan Corbet
2025-10-29 21:51 Stephen Rothwell
2025-10-29 22:22 ` Jonathan Corbet
2025-10-31 6:23 ` Alex Shi
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=20180510154359.4aea2351@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.