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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2143236.hFqxAeOdFG@bentobox>
Date:   Tue, 21 May 2019 09:18:21 +0200
From:   Sven Eckelmann <sven@...fation.org>
To:     Jonathan Corbet <corbet@....net>
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 Monday, 20 May 2019 23:54:23 CEST Jonathan Corbet wrote:
[...]
> Argh, sorry, I should have caught that.  Fixed, thanks.

Thanks for trying. Unfortunately it was changed to the wrong value. The actual 
commit I wanted to reference in both places of the commit message was:

    8ea8814fcdcb ("LICENSES: Clearly mark dual license only licenses")

It seems I've copied the wrong commit id for some reason when I send it though 
the git-fixes alias and it didn't occur to me that I just referenced my own 
patch. Sorry about the confusion.

Kind regards,
	Sven
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ