From: Jakub Narebski <jnareb@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Thiago Farina <tfransosi@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Trivial fix: Display a more friendly message with git-shell.
Date: Tue, 22 Sep 2009 01:17:18 -0700 (PDT) [thread overview]
Message-ID: <m3fxafbdh0.fsf@localhost.localdomain> (raw)
In-Reply-To: <vpqr5tzqvzm.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Thiago Farina <tfransosi@gmail.com> writes:
>
>> Hi Matthieu
>> On Mon, Sep 21, 2009 at 3:45 AM, Matthieu Moy
>> <Matthieu.Moy@grenoble-inp.fr> wrote:
>>> Perhaps one more line saying what 'man git-shell' says in addition
>>> would help:
>>>
>>> $ git-shell
>>> git-shell: Restricted login shell for GIT-only SSH access
>>> Usage: ...
>> I added this line to the output usage, but would be good to show the
>> commands that git-shell accept too?
>
> Well, at some point, I think the user will have to read the man page.
> I find it better to have a non-agressive error message, but I'm not
> sure it's relevant to try to give the complete manual here.
Perhaps:
$ git-shell
git-shell: Restricted login shell for GIT-only SSH access
This shell cannot be used as a login (interactive) shell
and/or
$ ssh user@repo.example.com
This user is restricted to GIT-only SSH access
(or something like that, especially in the second case).
I don't think giving 'Usage:' here would be a good idea, as this
program is not meant for end user, but for automatic use.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-09-22 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 17:11 [PATCH] Trivial fix: Display a more friendly message with git-shell Thiago Farina
2009-09-21 4:21 ` Tay Ray Chuan
2009-09-21 6:17 ` Johannes Sixt
2009-09-21 6:45 ` Matthieu Moy
2009-09-21 20:45 ` Thiago Farina
2009-09-22 7:28 ` Matthieu Moy
2009-09-22 8:15 ` Heiko Voigt
2009-09-22 8:17 ` Jakub Narebski [this message]
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=m3fxafbdh0.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=tfransosi@gmail.com \
/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).