Re: What's cooking in git.git (topics)

From: Pieter de Bie <pdebie@ai.rug.nl>
Date: Jun 24, 2008, 08:12 UTC
Message-ID: <9B8F0B10-F48D-475B-BF59-CEE94222B6E8@ai.rug.nl>
In-Reply-To: <7vwskfclfs.fsf@gitster.siamese.dyndns.org>

On 24 jun 2008, at 09:59, Junio C Hamano wrote:

Show 8 quoted lines

> The idea of the "shell: accept 'git foo' form" patch is that as long  
> as
> the server end consistently use the same version (i.e. git-shell is  
> from
> 'next' and it knows where the rest of git is installed), things should
> work fine.  I've merged them to 'next' and pushed it out so that you  
> can
> try it.

Any clone / push operation fails if you use current next:

Vienna:bin pieter$ git --version git version 1.5.6.129.g274ea Vienna:bin pieter$ git clone localhost:project/bonnenteller Initialize bonnenteller/.git Initialized empty Git repository in /opt/git/bin/bonnenteller/.git/ Password: bash: git-upload-pack: command not found fatal: The remote end hung up unexpectedly

I think that is what Miklos meant. Also, I think the client sends the command to execute on the remote side. At least for v1.5.5 clients and before, that is "git-upload-pack". As this is not in PATH, that command will fail on any server that runs v1.5.6 and has the libexec dir.

- Pieter