linux-kernel - Re: linux-next: Fixes tag needs some work in the jc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190521130431.2ab4c8f7@lwn.net>
Date:   Tue, 21 May 2019 13:04:31 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Sven Eckelmann <sven@...fation.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the jc_docs tree

On Tue, 21 May 2019 20:52:46 +0200
Sven Eckelmann <sven@...fation.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