From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>
Subject: Re: Git Daemon Dummy: 301 Redirects for git:// to https://
Date: Tue, 23 Feb 2016 16:11:46 +0100 [thread overview]
Message-ID: <CAHmME9qdK-NQ7Kz3JmH5PDwU9JnCG=TC1ipCisd0qffTMwAxYA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pVuo+Wub3=DuY-4Zy0Gjm1qM6empt3vvx9JcarF-rbcA@mail.gmail.com>
On Tue, Feb 23, 2016 at 4:11 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> That's interesting. I didn't realize that even the smart protocol was
> not as efficient as HTTP
Can't type today. *as efficient as git://
next prev parent reply other threads:[~2016-02-23 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 2:32 Git Daemon Dummy: 301 Redirects for git:// to https:// Jason A. Donenfeld
2016-02-23 6:15 ` Jeff King
2016-02-23 12:13 ` Duy Nguyen
2016-02-23 15:11 ` Jason A. Donenfeld
2016-02-23 15:11 ` Jason A. Donenfeld [this message]
2016-02-23 10:51 ` John Keeping
2016-02-23 15:10 ` Jason A. Donenfeld
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='CAHmME9qdK-NQ7Kz3JmH5PDwU9JnCG=TC1ipCisd0qffTMwAxYA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).