From: Michael Tremer <michael.tremer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Retiring git://
Date: Fri, 25 Jul 2025 15:10:44 +0100 [thread overview]
Message-ID: <6D23518A-3056-488E-A1D0-BE9AFD456D3D@ipfire.org> (raw)
Hello everyone,
Happy Friday!
This is a bit of a brief announcement that we no longer offer our Git repositories to be cloned using the git:// protocol. This is because I updated the server that is hosting the repositories to Debian 13 which no longer has the git-daemon package. Since the protocol is not encrypted and there has been low usage anyways, this should not be a problem for anyone. As an alternative, there is of course the https:// protocol available to clone your favourite Git repositories.
Best,
-Michael
reply other threads:[~2025-07-25 14:10 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=6D23518A-3056-488E-A1D0-BE9AFD456D3D@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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