From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git and "dumb protocols"
Date: Thu, 02 Nov 2006 13:12:53 +0100 [thread overview]
Message-ID: <eicnbe$v6l$1@sea.gmane.org> (raw)
In-Reply-To: vpq4ptixdfj.fsf@ecrins.imag.fr
Matthieu Moy wrote:
> I'll probably do, but my concern is broader than that. I like the
> ability to use almost any webhosting service for my revision control.
> GNU Arch was quite good at that, bzr is also (doesn't support webdav
> very well yet, but read-only-HTTP, sftp and ftp are there), so I'd
> like git to do the same.
Well, git can fetch (read) via http, https, ftp, sftp, rsync, git, ssh+git;
it can push via http(s) with WebDAV, and ssh+git (ssh+git meaning via ssh,
with git installed on the server side).
BTW. rsync is considered obsolete, and suitable only for initial cloning,
perhaps.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-02 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 10:36 git and "dumb protocols" Matthieu Moy
2006-11-02 10:42 ` Andy Whitcroft
2006-11-02 10:48 ` Petr Baudis
2006-11-02 10:57 ` Johannes Schindelin
2006-11-02 11:02 ` Petr Baudis
2006-11-02 12:04 ` Matthieu Moy
2006-11-02 12:12 ` Jakub Narebski [this message]
2006-11-02 12:21 ` Petr Baudis
2006-11-03 23:27 ` Daniel Barkalow
2006-11-02 10:51 ` Johannes Schindelin
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='eicnbe$v6l$1@sea.gmane.org' \
--to=jnareb@gmail.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