Re: git and "dumb protocols"

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Nov 2, 2006, 12:04 UTC
Message-ID: <vpq4ptixdfj.fsf@ecrins.imag.fr>
In-Reply-To: <20061102104848.GH20017@pasky.or.cz>

Petr Baudis <pasky@suse.cz> writes:

>   yes, you can push using HTTP DAV - just push to an HTTP URL; make sure
> you have git-http-push compiled, it is sometimes not compiled because it
> unfortunately adds dependencies on couple of more libraries.

That's great. I don't need this right now, but having worked behind a firewall + proxy, I know how appreciable it is to push with DAV ;-).

Show 5 quoted lines

>   I think a patch that would add support for pushing over sftp or some
> other dumb protocol would be welcome. One problem is with proper locking
> of ref updates (not sure how well would sftp cope with that), another is
> that you will need to do git-update-server-info's job on the server
> side.

It should be possible (but not implemented AAUI) also to generate the additional info of git-update-server-info on the client, isn't it?

>   If you already have SSH access to the server, why not compile Git
> there and install it to your $HOME, though?

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.

And yes, there are tons of reasons not to install git on the server. In particular, the fact that I'm not root there, and too lazy to do more than "aptitude install git" with pleasure ;-).