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: <20200716132134.56cb4bc1@endymion>
Date:   Thu, 16 Jul 2020 13:21:34 +0200
From:   Jean Delvare <jdelvare@...e.de>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: failing to fetch the dmi tree

Hi Stephen,

On Wed, 15 Jul 2020 11:37:43 +0200, Jean Delvare wrote:
> On Mon, 13 Jul 2020 09:11:02 +1000, Stephen Rothwell wrote:
> > Jean, I don't suppose you would like to produce a git tree for me to
> > fetch instead, as yours is the last quilt series I fetch (apart from
> > Andrew's which is special).  
> 
> Actually, feel free to suppose. While a quilt tree fits my current
> workflow better, I don't want to be the guy who makes your life more
> difficult. Let me give it a try.

OK, so my old for-next branch in quilt format is still at:

http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/

and what should be a git equivalent of it is at:

git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git dmi-for-next

If the latter works for you then I shall be ready to switch to it
officially. If there's anything wrong, please let me know.

Will you curse me if I ever rebase this branch?

Thanks,
-- 
Jean Delvare
SUSE L3 Support

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ