From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Stefan Beller <sbeller@google.com>
Cc: Jeff King <peff@peff.net>, git <git@vger.kernel.org>
Subject: Re: main url for linking to git source?
Date: Tue, 8 May 2018 01:51:30 +0000 [thread overview]
Message-ID: <20180508015130.GN953644@genre.crustytoothpaste.net> (raw)
In-Reply-To: <CAGZ79kZVdiEOO+b_Ygrfw1D9uV1T5TYBS580zPaZeYoMRfNuUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Mon, May 07, 2018 at 11:15:46AM -0700, Stefan Beller wrote:
> There I would try to mirror Junios list of "public repositories"
> https://git-blame.blogspot.com/p/git-public-repositories.html
> without officially endorsing one over another.
I think I would also prefer a list of available repositories over a
hard-coded choice. It may be that some places (say, Australia) have
better bandwidth to one over the other, and users will be able to have a
better experience with certain mirrors.
While I'm sympathetic to the idea of referring to kernel.org because
it's open-source and non-profit, users outside of North America are
likely to have a less stellar experience with its mirrors, since they're
all in North America.
I would suggest that whatever option we choose, we only specify HTTPS or
SSH (i.e., encrypted) protocols. Encryption is cheap, and we have lots
of options meeting that criterion.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-05-08 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 6:37 main url for linking to git source? Jeff King
2018-05-07 11:38 ` Johannes Schindelin
2018-05-07 14:20 ` Konstantin Ryabitsev
2018-05-07 12:18 ` Junio C Hamano
2018-05-07 18:15 ` Stefan Beller
2018-05-08 1:51 ` brian m. carlson [this message]
2018-05-08 2:46 ` Konstantin Ryabitsev
2018-05-08 3:26 ` Junio C Hamano
2018-05-08 12:55 ` brian m. carlson
2018-05-08 6:43 ` Kaartic Sivaraam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180508015130.GN953644@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).