From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: pavlix <pavlix@pavlix.net>
Cc: git@vger.kernel.org
Subject: Re: GIT push to sftp (feature request)
Date: Mon, 6 Aug 2007 09:12:41 +1200 [thread overview]
Message-ID: <46a038f90708051412p722aa906v73e986a805f1558b@mail.gmail.com> (raw)
In-Reply-To: <200708051105.44376.pavlix@pavlix.net>
On 8/5/07, pavlix <pavlix@pavlix.net> wrote:
> Did I miss something?
Unfortunately, git does not "push" over protocols that cannot execute
git on the remote server. We call them "dumb protocols" and if you
search this list for that name, you'll find lots.
Git tries to be smart in at least 2 ways that don't work with dump
protocols: it works locklessly (yet it performs atomic updates) and it
sends only the objects needed over the wire (saving a lot of
bandwidth).
Using dumb protocols it's impossible to do either. And these days it's
not that hard to setup git (or any other binary) to execute at the
remote end.
Bazaar-NG and others do support dumb protocols, and (I think) they do
it by using one big lock over the repo. But the lock is not safe, and
things can (and do) go wrong with weak locking schemes.
git used to support rsync -- but I don't think that works anymore for
pushes. Other than git over ssh, perhaps you can try the apache module
that implements git over http?
hope that helps,
martin
next prev parent reply other threads:[~2007-08-05 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 9:05 GIT push to sftp (feature request) pavlix
2007-08-05 13:38 ` Johannes Schindelin
2007-08-05 21:12 ` Martin Langhoff [this message]
2007-08-05 22:20 ` Matthieu Moy
2007-08-06 0:00 ` Martin Langhoff
2007-08-06 8:59 ` Matthieu Moy
2007-08-06 0:14 ` Jakub Narebski
2007-08-07 21:50 ` Jan Hudec
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=46a038f90708051412p722aa906v73e986a805f1558b@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=pavlix@pavlix.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).