netdev - Re: pull-request: can-next 2018-11-28,pull-request: can-next 2018-11-28

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: <20181128.112157.1875553528431620394.davem@davemloft.net>
Date:   Wed, 28 Nov 2018 11:21:57 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     mkl@...gutronix.de
Cc:     netdev@...r.kernel.org, kernel@...gutronix.de,
        linux-can@...r.kernel.org
Subject: Re: pull-request: can-next 2018-11-28,pull-request: can-next
 2018-11-28

From: Marc Kleine-Budde <mkl@...gutronix.de>
Date: Wed, 28 Nov 2018 17:01:13 +0100

>   ssh://git@...olite.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-4.21-20181128

This doesn't work for me at all.

I'm not adding a custom .ssh config entry to point gitolite.kernel.org
to the same SSH key that I use for gitolite@...kernel.org, no way.

I don't want to see these SSH based URLs any more, they are a pain and
add overhead to my workflow.

Please just use plain git:// URLs, thank you.