From: Greg Brockman <gdb@MIT.EDU>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>, Petr Baudis <pasky@suse.cz>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] shell: Rewrite documentation and improve error message
Date: Mon, 23 Aug 2010 13:42:12 -0400 [thread overview]
Message-ID: <AANLkTintw7=25nsr-7NjE_-xJqMab_HggjPOtSHBf109@mail.gmail.com> (raw)
In-Reply-To: <20100822080359.GB15561@kytes>
> -COMMAND_DIR is the path 'git-shell-commands' in the user's home
> -directory. The user must have read and execute permissions to the
> -directory for it to be useful.
> +COMMAND_DIR is the path "$HOME/git-shell-commands". The user must have
> +read and execute permissions to the directory in order to execute the
> +programs in it. The programs are executed with a cwd of $HOME, and
> +<argument> is passed to them as a command-line argument.
Sorry, I guess I wasn't clear enough with what I meant here. The
<argument> is actually parsed as a command-line string (so split on
spaces respecting quotes), not just passed as a raw command-line
argument.
> if (access(COMMAND_DIR, R_OK | X_OK) == -1) {
> - die("Inteactive git shell is not enabled.\n"
> - "hint: " COMMAND_DIR " should exist "
> + die("Interactive git shell is not enabled.\n"
> + "hint: ~/$COMMAND_DIR should exist "
> "and have read and execute access.");
> }
> run_shell();
Whoops, I'm not sure why I put a $ here. "hint: ~/" COMMAND_DIR "
should exist " is definitely what you want.
Other than that, looks fine to me.
next prev parent reply other threads:[~2010-08-23 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 19:44 [PATCH] shell: Rewrite documentation and improve error message Ramkumar Ramachandra
2010-08-20 19:51 ` Ramkumar Ramachandra
2010-08-22 6:00 ` Greg Brockman
2010-08-22 8:04 ` [PATCH v2] " Ramkumar Ramachandra
2010-08-23 17:42 ` Greg Brockman [this message]
2010-08-24 5:36 ` [PATCH v3] " Ramkumar Ramachandra
2010-08-24 5:43 ` Greg Brockman
2010-08-24 12:35 ` Ramkumar Ramachandra
2010-08-24 15:22 ` Greg Brockman
2010-08-24 19:01 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTintw7=25nsr-7NjE_-xJqMab_HggjPOtSHBf109@mail.gmail.com' \
--to=gdb@mit.edu \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).