From: Sven Eckelmann <sven@narfation.org>
To: Jonathan Corbet <corbet@lwn.net>
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: Fixes tag needs some work in the jc_docs tree
Date: Tue, 21 May 2019 20:23:48 +0200 [thread overview]
Message-ID: <1654747.HbZAs67LzE@sven-edge> (raw)
In-Reply-To: <20190521093107.79790d12@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
On Tuesday, 21 May 2019 17:31:07 CEST Jonathan Corbet wrote:
> <sigh>
It is ok, I will never send you any patch again.
> We want those tags to be right. I'm going to fix this and force-push,
> hopefully nobody will get too made at me...
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-21 18:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 21:44 linux-next: Fixes tag needs some work in the jc_docs tree Stephen Rothwell
2019-05-20 21:54 ` Jonathan Corbet
2019-05-21 7:18 ` Sven Eckelmann
2019-05-21 15:31 ` Jonathan Corbet
2019-05-21 18:23 ` Sven Eckelmann [this message]
2019-05-21 18:46 ` Jonathan Corbet
2019-05-21 18:52 ` Sven Eckelmann
2019-05-21 19:04 ` Jonathan Corbet
2019-05-21 19:05 ` Sven Eckelmann
2019-05-21 7:12 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2021-01-21 20:57 Stephen Rothwell
2021-02-25 21:34 Stephen Rothwell
2021-02-25 21:39 ` Jonathan Corbet
2021-02-25 22:01 ` Stephen Rothwell
2021-02-25 22:35 ` Andrew Donnellan
2022-01-06 23:36 Stephen Rothwell
2022-01-07 10:25 ` James Clark
2022-01-07 16:19 ` Randy Dunlap
2022-01-10 10:30 ` James Clark
2022-01-07 16:35 ` Jonathan Corbet
2022-03-28 20:58 Stephen Rothwell
2023-07-03 21:54 Stephen Rothwell
2023-07-03 23:46 Stephen Rothwell
2023-07-04 14:32 ` 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=1654747.HbZAs67LzE@sven-edge \
--to=sven@narfation.org \
--cc=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 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).