From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Fri, 5 Jun 2020 14:34:33 -0600 [thread overview]
Message-ID: <20200605143433.578aaaf5@lwn.net> (raw)
In-Reply-To: <ba5ca7c6-bdf9-b568-b58e-d6d466dc668f@al2klimov.de>
On Fri, 5 Jun 2020 22:28:54 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:
> Am I completely blind or did the patch completely disappear?
>
> $ git log v5.0..docs-5.8 |grep -Fwe 'Alexander A. Klimov'
> $ git log v5.0..lwn/docs-next |grep -Fwe 'Alexander A. Klimov'
> $ git log v5.0..lwn/docs-next-merge |grep -Fwe 'Alexander A. Klimov'
> $ git log v5.0..torvalds/master |grep -Fwe 'Alexander A. Klimov'
I pulled the original version since it wasn't properly signed off. I have
your replacement, and may yet get it in during the merge window.
(Please don't top-post).
jon
next prev parent reply other threads:[~2020-06-05 20:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 22:01 linux-next: Signed-off-by missing for commit in the jc_docs tree Stephen Rothwell
2020-05-26 14:44 ` Jonathan Corbet
2020-06-05 20:28 ` Alexander A. Klimov
2020-06-05 20:34 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 6:11 Stephen Rothwell
2023-01-19 21:34 Stephen Rothwell
2023-01-19 21:48 ` Jonathan Corbet
2023-01-19 21:59 ` Jakob Koschel
2020-10-21 21:55 Stephen Rothwell
2020-10-21 22:19 ` Jonathan Corbet
2020-10-22 6:55 ` Zheng, Fam
2020-08-24 23:13 Stephen Rothwell
2020-08-24 23:18 ` Jonathan Corbet
2019-06-26 22:01 Stephen Rothwell
2019-06-26 22:09 ` Jonathan Corbet
2018-05-10 21:40 Stephen Rothwell
2018-05-10 21:44 ` Jonathan Corbet
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=20200605143433.578aaaf5@lwn.net \
--to=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--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 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).