From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Simon Josefsson <simon@josefsson.org>
Subject: Re: [PATCH] Use https:// instead of git://.
Date: Sun, 10 Jan 2021 20:22:03 +0100 [thread overview]
Message-ID: <6c42d113-bba1-2ca9-bd02-d572ab6c4f3b@bernhard-voelker.de> (raw)
In-Reply-To: <1632853.gvciFGaia7@omega>
On 1/10/21 5:14 PM, Bruno Haible wrote:
> "https://git.savannah.gnu.org/git/myproject.git -
> encrypted read-only anonymous smart http access"
Nice, then https:// seems indeed to be better than git://.
Have a nice day,
Berny
next prev parent reply other threads:[~2021-01-10 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 0:09 [PATCH] Use https:// instead of git:// Simon Josefsson via Gnulib discussion list
2021-01-10 1:30 ` Bruno Haible
2021-01-10 10:34 ` Simon Josefsson via Gnulib discussion list
2021-01-10 12:20 ` Simon Josefsson via Gnulib discussion list
2021-01-10 15:18 ` Bernhard Voelker
2021-01-10 16:14 ` Bruno Haible
2021-01-10 19:22 ` Bernhard Voelker [this message]
2021-01-10 1:58 ` Jeffrey Walton
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: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c42d113-bba1-2ca9-bd02-d572ab6c4f3b@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.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 read-only IMAP folder(s) and NNTP newsgroup(s).