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: <CAHk-=wgJH3dgztETpQ4CaseA+j9rgbk0XP_yXDGshmQxAh3RKw@mail.gmail.com>
Date:   Fri, 25 Mar 2022 09:57:05 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Max Filippov <jcmvbkbc@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "open list:TENSILICA XTENSA PORT (xtensa)" 
        <linux-xtensa@...ux-xtensa.org>, Chris Zankel <chris@...kel.net>
Subject: Re: [PULL 00/18] xtensa updates for v5.18

On Fri, Mar 25, 2022 at 8:49 AM Max Filippov <jcmvbkbc@...il.com> wrote:
>
> (btw, I've noticed that github removed support for the unauthenticated
>  git:// protocol. Should I send pull request URLs using ssh or https?)

I suspect for consistency, using https:// is the way to go.

I'm a bit sad to see "git:" go, since that was visually such a good
marker that it's about a _git_ server, not some random web page (and I
rely on the signed tag, not on some https thing).

But from a technical angle, I guess it was inevitable. And git is
everywhere, and 'github' certainly makes that "it's a git repo" part
obvious anyway, so.

                    Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ