From: tycho garen <email@example.com>
To: "Sébastien Vauban" <firstname.lastname@example.org>
Subject: Re: Re: Worg pull broken?
Date: Wed, 27 Oct 2010 07:07:47 -0400 [thread overview]
Message-ID: <20101027110747.GB11502@deleuze> (raw)
On Wed, Oct 27, 2010 at 09:47:24AM +0200, Sébastien Vauban wrote:
> - Does using ssh give you compression for free? Hence, a quicker way to
> download big repos?
Git can interact with the remote repository differently, allowing it
to do some de-duplication over SSH that it can't do over HTTP. Also,
depending on your SSH configurations SSH can (and generally is, I
think, correct me if I'm wrong) somewhat compressed (But then, so is
HTTP with DEFLATE/gzip sometimes). This might not speed up the
operation both because of the processor overhead to do the
compression, but also because SSH's encryption takes a bit of
Basically, "it depends on what free is," and pragmatically git pull's
over SSH are quicker than git pulls over HTTP.
> - Can you use whatever protocol (git, http, git+ssh) in front of any "git
> URL"? I mean, if I see on the Web, http://xxx.git, can I replace http by
> git with no impact?
No. SSH (and git) protocols specify the path of the file based on
where the file lives on the host machines file system. Start at the
root / (or chroot) in the top level and go from there. The paths for
HTTP are dependent upon the configuration of the web server and are
often somewhat distinct from what is actually going on in the file
system given virtual hosting and URL rewriting.
Hope this helps.
"don't get it right, get it written" -- james thurber
next prev parent reply other threads:[~2010-10-27 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 15:55 Worg pull broken? Sébastien Vauban
2010-10-24 19:06 ` David Maus
2010-10-27 7:47 ` Sébastien Vauban
2010-10-27 11:07 ` tycho garen [this message]
2010-11-05 9:32 ` Sébastien Vauban
2010-11-05 18:48 ` David Maus
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).