From: Jeff King <peff@peff.net>
To: Neal Kreitzinger <nkreitzinger@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: msysgit with git protocol to linux server
Date: Fri, 18 May 2012 19:57:46 -0400 [thread overview]
Message-ID: <20120518235746.GA765@sigill.intra.peff.net> (raw)
In-Reply-To: <jp69f2$gir$1@dough.gmane.org>
On Fri, May 18, 2012 at 02:55:13PM -0500, Neal Kreitzinger wrote:
> If my pc is on the same vpn as the linux server can I use git
> protocol instead of ssh for better speed?
Yes, you can, but no, it will probably not be faster.
> I have instructions on how to setup msysgit with ssh. (I'm new to
> msysgit and ssh.) On the linux servers we've been using git protocol
> since they are on the same vpn. My understanding is that git
> protocol is faster than ssh.
It's exactly the same protocol. The only reason it would be faster is
if your machine is so slow that the encryption overhead of ssh is a
bottleneck.
Note that git-over-http can be slightly slower than the regular git
protocol, because there may be more round-trip latency during the commit
negotiation (but once you are actually getting the pack from the server,
it should be the same, and that time tends to dominate, anyway).
I'm not sure why you care about the vpn, unless:
1. You are worried about man-in-the-middle attacks fetching via
git://, which you can presumably disregard over the vpn.
2. You want to allow pushes over git:// instead of ssh. I wouldn't
recommend this, but you can do so by setting daemon.receivepack in
the config.
-Peff
next prev parent reply other threads:[~2012-05-18 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 19:55 msysgit with git protocol to linux server Neal Kreitzinger
2012-05-18 23:57 ` Jeff King [this message]
2012-05-19 8:14 ` Johannes Sixt
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=20120518235746.GA765@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=nkreitzinger@gmail.com \
/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).