summaryrefslogtreecommitdiff
path: root/git-sh-setup.sh
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-01-07 10:17:52 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-01-08 05:36:35 (GMT)
commit4b441f47cefe7f4861167a151a395606e1a16745 (patch)
tree745a824bf251e485fc6bd6649bddc992b395994c /git-sh-setup.sh
parent7d1864ce67d83485cf5cbc8c90fc170ee884ef16 (diff)
downloadgit-4b441f47cefe7f4861167a151a395606e1a16745.zip
git-4b441f47cefe7f4861167a151a395606e1a16745.tar.gz
git-4b441f47cefe7f4861167a151a395606e1a16745.tar.bz2
git-fetch: allow updating the current branch in a bare repository.
Sometimes, people have only fetch access into a bare repository that is used as a back-up location (or a distribution point) but does not have a push access for networking reasons, e.g. one end being behind a firewall, and updating the "current branch" in such a case is perfectly fine. This allows such a fetch without --update-head-ok, which is a flag that should never be used by end users otherwise. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-sh-setup.sh')
-rwxr-xr-xgit-sh-setup.sh8
1 files changed, 8 insertions, 0 deletions
diff --git a/git-sh-setup.sh b/git-sh-setup.sh
index 87b939c..7fdc912 100755
--- a/git-sh-setup.sh
+++ b/git-sh-setup.sh
@@ -28,6 +28,14 @@ set_reflog_action() {
fi
}
+is_bare_repository () {
+ git-repo-config --bool --get core.bare ||
+ case "$GIT_DIR" in
+ .git | */.git) echo false ;;
+ *) echo true ;;
+ esac
+}
+
if [ -z "$LONG_USAGE" ]
then
LONG_USAGE="Usage: $0 $USAGE"