Ramkumar Ramachandra wrote:
> Jonathan Nieder wrote:
>> * If the file ~/git-shell-commands/no-interactive-login exists,
>>run no-interactive-login to let the server say what it likes,
>>then hang up.
[...]
> If "no-interactive-login" doesn't have execute permissions, we'll get
> an error
Jonathan Nieder wrote:
> * If the file ~/git-shell-commands/no-interactive-login exists,
>run no-interactive-login to let the server say what it likes,
>then hang up.
>
> * Otherwise, if ~/git-shell-commands/ is present, start an
>interactive read-eval-print loop.
>
> * Otherwise, pr
Junio C Hamano wrote:
> Jonathan Nieder writes:
>> If I disable git-shell's interactive mode by removing the
>> ~/git-shell-commands directory, attempts to use 'ssh' in produce a
>> message intended for the administrator:
>
> Sorry, but -ECANTPARSE. s/in produce/produces/ perhaps? Or if you
> m
Jonathan Nieder writes:
> If I disable git-shell's interactive mode by removing the
> ~/git-shell-commands directory, attempts to use 'ssh' in produce a
> message intended for the administrator:
Sorry, but -ECANTPARSE. s/in produce/produces/ perhaps? Or if you
meant "ssh in" as a verb, then "a
If I disable git-shell's interactive mode by removing the
~/git-shell-commands directory, attempts to use 'ssh' in produce a
message intended for the administrator:
$ ssh git@myserver
fatal: Interactive git shell is not enabled.
hint: ~/git-shell-commands should exist and h
5 matches
Mail list logo
