From: "Shawn O. Pearce" <spearce@spearce.org>
To: John Dlugosz <JDlugosz@TradeStation.com>
Cc: git@vger.kernel.org
Subject: Re: Windows Server?
Date: Wed, 29 Apr 2009 08:24:37 -0700 [thread overview]
Message-ID: <20090429152437.GC23604@spearce.org> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70AE3F27E@EXCHANGE.trad.tradestation.com>
John Dlugosz <JDlugosz@TradeStation.com> wrote:
> > But yes, the SSH protocol is the git:// protocol, tunneled through
> SSH,
> > and will be much more efficient over the VPN than SMB.
>
> Someone else said that the git daemon is for fetching only. So that's
> not a limitation with the git: protocol, just the git-daemon itself?
Correct. Actually, git-daemon can support pushing. Its just that
it has *no* authentication, so enabling push support on the daemon
is really risky as anyone who has network access to the server can
update the repositories it hosts.
--
Shawn.
prev parent reply other threads:[~2009-04-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 22:41 Windows Server? John Dlugosz
2009-04-28 22:46 ` Thomas Adam
2009-04-29 15:18 ` John Dlugosz
2009-04-28 22:46 ` Shawn O. Pearce
2009-04-29 15:22 ` John Dlugosz
2009-04-29 15:24 ` Shawn O. Pearce [this message]
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=20090429152437.GC23604@spearce.org \
--to=spearce@spearce.org \
--cc=JDlugosz@TradeStation.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).