Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
MIME-Version: 1.0
References: <20220325154848.107863-1-jcmvbkbc@gmail.com>
In-Reply-To: <20220325154848.107863-1-jcmvbkbc@gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 25 Mar 2022 09:57:05 -0700
Message-ID: <CAHk-=wgJH3dgztETpQ4CaseA+j9rgbk0XP_yXDGshmQxAh3RKw@mail.gmail.com>
Subject: Re: [PULL 00/18] xtensa updates for v5.18
To:     Max Filippov <jcmvbkbc@gmail.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "open list:TENSILICA XTENSA PORT (xtensa)" 
        <linux-xtensa@linux-xtensa.org>, Chris Zankel <chris@zankel.net>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Mar 25, 2022 at 8:49 AM Max Filippov <jcmvbkbc@gmail.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