unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org
Subject: git: vs https: (was: [nongnu] main d1d82e3c06 1/2: * Makefile (admin): Use https:// instead of git:// for the URI)
Date: Tue, 20 Dec 2022 14:56:16 -0500	[thread overview]
Message-ID: <jwvpmcd5072.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20221218213656.431DDC00619@vcs2.savannah.gnu.org> (Sean Whitton's message of "Sun, 18 Dec 2022 16:36:56 -0500 (EST)")

>     * Makefile (admin): Use https:// instead of git:// for the URI.

I used `git:` because fetching a single branch over `https:` was *much*
slower.  AFAIK, this was because `git.sv.gnu.org` didn't run Git's
"smart HTTP" on its https server.

I just tried it again, it seems that `https:` is now as fast as `git:`, tho.
Was I just lucky, or has the problem really been fixed?


        Stefan




  parent reply	other threads:[~2022-12-20 19:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167139941586.12438.1105626110857907494@vcs2.savannah.gnu.org>
     [not found] ` <20221218213656.56E0AC0061B@vcs2.savannah.gnu.org>
2022-12-20 19:44   ` [nongnu] main 385623dca6 2/2: * elpa-packages (notmuch): New package Stefan Monnier
2022-12-20 23:36     ` Sean Whitton
2022-12-21  5:01       ` Stefan Monnier
2022-12-21  5:42         ` Sean Whitton
2022-12-21  6:11           ` Stefan Monnier
2022-12-21  8:57         ` Philip Kaludercic
2022-12-22  4:03           ` Stefan Monnier
2022-12-22 20:48             ` Sean Whitton
2022-12-24 11:09               ` Philip Kaludercic
2022-12-24 18:13                 ` Sean Whitton
2022-12-24 19:33                   ` Philip Kaludercic
2022-12-22 21:02             ` Dmitry Gutov
2022-12-22 22:13               ` Stefan Monnier
2022-12-22 22:52                 ` Andreas Schwab
2022-12-24 14:37                   ` Philip Kaludercic
2022-12-24 14:40                     ` Andreas Schwab
2022-12-24 15:02                       ` Philip Kaludercic
2022-12-24 15:27                         ` Andreas Schwab
2022-12-24 15:48                           ` Philip Kaludercic
2022-12-24 16:06                             ` Andreas Schwab
2022-12-24 16:57                               ` Philip Kaludercic
2022-12-21  8:45       ` Philip Kaludercic
2022-12-22 20:53         ` Sean Whitton
2022-12-20 23:39     ` Sean Whitton
     [not found]       ` <871qot1w7e.fsf-GqYU2JSbRdm5XZx3jhULPQVB4TfmtpSe@public.gmane.org>
2022-12-21 11:53         ` David Bremner
2022-12-22 20:54           ` Sean Whitton
     [not found] ` <20221218213656.431DDC00619@vcs2.savannah.gnu.org>
2022-12-20 19:56   ` Stefan Monnier [this message]
2022-12-20 23:18     ` git: vs https: Sean Whitton
2022-12-21  4:35       ` Stefan Monnier
2022-12-21  8:45       ` Andreas Schwab

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvpmcd5072.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=spwhitton@spwhitton.name \
    /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://git.savannah.gnu.org/cgit/emacs.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).