From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Corbet Subject: Re: linux-next: Fixes tag needs some work in the jc_docs tree Date: Tue, 21 May 2019 13:04:31 -0600 Message-ID: <20190521130431.2ab4c8f7@lwn.net> References: <20190521074435.7a277fd6@canb.auug.org.au> <1654747.HbZAs67LzE@sven-edge> <20190521124603.658acbd3@lwn.net> <1640847.rHWZmc4HWd@sven-edge> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <1640847.rHWZmc4HWd@sven-edge> Sender: linux-kernel-owner@vger.kernel.org To: Sven Eckelmann Cc: Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List List-Id: linux-next.vger.kernel.org On Tue, 21 May 2019 20:52:46 +0200 Sven Eckelmann 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 "" > 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