From: ori@eigenstate.org
To: 9front@9front.org
Subject: [9front] github and git://
Date: Wed, 01 Sep 2021 20:54:53 -0400 [thread overview]
Message-ID: <DB6789FC53E71D021351E7666A3E58B9@eigenstate.org> (raw)
github is turning off support for git:// clone urls;
if you've cloned repos from them over git://, then
they're going to stop working at some point.
We support https:// clones, so if this happens, just
open .git/config, and replace 'git://' with https://.
https://github.blog/2021-09-01-improving-git-protocol-security-github/
reply other threads:[~2021-09-02 1:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB6789FC53E71D021351E7666A3E58B9@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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.
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 NNTP newsgroup(s).