From: Jonathan Corbet <corbet@lwn.net>
To: Sven Eckelmann <sven@narfation.org>
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 13:04:31 -0600 [thread overview]
Message-ID: <20190521130431.2ab4c8f7@lwn.net> (raw)
In-Reply-To: <1640847.rHWZmc4HWd@sven-edge>
On Tue, 21 May 2019 20:52:46 +0200
Sven Eckelmann <sven@narfation.org> wrote:
> > I'm hoping that's meant to be a joke...? This is certainly not a big
> > problem on any scale...
>
> Not really. If you are so frustrated that you start your reply with "<sigh>"
> then I think that it was not enough for me to explain what I did wrong and
> that I am sorry about copying the wrong git commit + not noticing it when
> pasting it to the commit message. What else should I do? Jump back in time?
It was just a sigh because there was a little mess that I needed to clean
up — one that I had failed to clean up correctly on my first attempt.
That's all. Apologies for giving you any other sort of impression, that
was not intended. Things happen, life goes on.
jon
next prev parent reply other threads:[~2019-05-21 19:04 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
2019-05-21 18:46 ` Jonathan Corbet
2019-05-21 18:52 ` Sven Eckelmann
2019-05-21 19:04 ` Jonathan Corbet [this message]
2019-05-21 19:05 ` Sven Eckelmann
2019-05-21 7:12 ` Sven Eckelmann
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=20190521130431.2ab4c8f7@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sven@narfation.org \
/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.