Bob Proulx <[email protected]> writes:

> Laurent Lyaudet wrote:
>> I stumbled upon this URL:
>> https://https.git.savannah.gnu.org/git/
>> and was surprised by the double https.
>
> Ah, yes, well, I admit I struggled with the naming.  Naming of things
> is one of the great challenges.
>
> But that URL is not one to be seen by humans though so it should not
> be a problem for humans to sort out.  That's the URL for git clients.
> And git clients being computer programs are never surprised as such by
> what they use or find there.

Oh, no. That *is* seen by humans. We need to give it for git clone
instructions. As a result, for example, it is staring right at the users
at https://orgmode.org/. Some users are confused.

> So git.savannah.gnu.org must be (at the moment anyway) the singleton
> host used for member ssh git push access.  Which means that if we want
> to build a distributed pool of servers to serve the other services
> around git then we need to use a different hostname for it.  This is
> where the new hostnames arrived.  One for each individual service
> which must be supported at Savannah.
>
>     git.git.savannah.gnu.org
>     https.git.savannah.gnu.org
>     http.git.savannah.gnu.org
>     gitweb.git.savannah.gnu.org
>     cgit.git.savannah.gnu.org
>
> I floated the naming around our internal SysOps team and various
> alternatives were discussed.  But in the end this naming survived as
> the most logical result.  And so here we are.  The name reflects the
> service it is providing.

What about simply mirror.git.savannah.gnu.org?

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Reply via email to