From: Greg Brockman <gdb@MIT.EDU>
To: jrnieder@gmail.com, j.sixt@viscovery.net, avarab@gmail.com,
gitster@pobox.com, git@vger.kernel.org, gdb@mit.edu
Subject: [PATCHv4 3/3] Add sample commands for git-shell
Date: Wed, 28 Jul 2010 00:43:04 -0700 [thread overview]
Message-ID: <1280302984-1752-4-git-send-email-gdb@mit.edu> (raw)
In-Reply-To: <1280302984-1752-1-git-send-email-gdb@mit.edu>
Provide a 'list' command to view available bare repositories ending in
.git and a 'help command to display usage. Also add documentation in
a README
Signed-off-by: Greg Brockman <gdb@mit.edu>
---
contrib/git-shell-commands/README | 18 ++++++++++++++++++
contrib/git-shell-commands/help | 16 ++++++++++++++++
contrib/git-shell-commands/list | 10 ++++++++++
3 files changed, 44 insertions(+), 0 deletions(-)
create mode 100644 contrib/git-shell-commands/README
create mode 100755 contrib/git-shell-commands/help
create mode 100755 contrib/git-shell-commands/list
This differs from v3 in that:
* the 'find' command in 'list' discards its stderr. This is useful for
avoiding noise from inaccessible directories or non-git repositories with
name matching '*.git'.
* the README does not mention that commands will be run from $(pwd)/git-shell-commands,
because they will now be run from $HOME/git-shell-commands.
diff --git a/contrib/git-shell-commands/README b/contrib/git-shell-commands/README
new file mode 100644
index 0000000..438463b
--- /dev/null
+++ b/contrib/git-shell-commands/README
@@ -0,0 +1,18 @@
+Sample programs callable through git-shell. Place a directory named
+'git-shell-commands' in the home directory of a user whose shell is
+git-shell. Then anyone logging in as that user will be able to run
+executables in the 'git-shell-commands' directory.
+
+Provided commands:
+
+help: Prints out the names of available commands. When run
+interactively, git-shell will automatically run 'help' on startup,
+provided it exists.
+
+list: Displays any bare repository whose name ends with ".git" under
+user's home directory. No other git repositories are visible,
+although they might be clonable through git-shell. 'list' is designed
+to minimize the number of calls to git that must be made in finding
+available repositories; if your setup has additional repositories that
+should be user-discoverable, you may wish to modify 'list'
+accordingly.
diff --git a/contrib/git-shell-commands/help b/contrib/git-shell-commands/help
new file mode 100755
index 0000000..a43fcd6
--- /dev/null
+++ b/contrib/git-shell-commands/help
@@ -0,0 +1,16 @@
+#!/bin/sh
+
+if tty -s; then
+ echo "Run 'help' for help, or 'exit' to leave. Available commands:"
+else
+ echo "Run 'help' for help. Available commands:"
+fi
+
+cd "$(dirname "$0")"
+
+for cmd in *; do
+ case "$cmd" in
+ help) ;;
+ *) [ -f "$cmd" ] && [ -x "$cmd" ] && echo "$cmd" ;;
+ esac
+done
diff --git a/contrib/git-shell-commands/list b/contrib/git-shell-commands/list
new file mode 100755
index 0000000..ffc5ac4
--- /dev/null
+++ b/contrib/git-shell-commands/list
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+print_if_bare_repo='
+ if "$(git --git-dir="$1" rev-parse --is-bare-repository)" = true
+ then
+ printf "%s\n" "${1#./}"
+ fi
+'
+
+find -type d -name "*.git" -exec sh -c "$print_if_bare_repo" -- \{} \; -prune 2>/dev/null
--
1.7.0.4
next prev parent reply other threads:[~2010-07-28 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 7:43 [PATCHv4 0/3] Updated patch series for providing mechanism to list available repositories Greg Brockman
2010-07-28 7:43 ` [PATCHv4 1/3] Allow creation of arbitrary git-shell commands Greg Brockman
2010-07-29 0:31 ` Greg Brockman
2010-07-29 0:37 ` Greg Brockman
2010-07-28 7:43 ` [PATCHv4 2/3] Add interactive mode to git-shell for user-friendliness Greg Brockman
2010-07-28 7:43 ` Greg Brockman [this message]
2010-07-28 17:23 ` [PATCHv4 0/3] Updated patch series for providing mechanism to list available repositories 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1280302984-1752-4-git-send-email-gdb@mit.edu \
--to=gdb@mit.edu \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jrnieder@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).