Also clarify failure to push to read-only remote. Especially,
state why rsync:// is not used for pushing.
[jc: ideally rsync should not be used for anything]
Signed-off-by: Chris Shoemaker <c.shoemaker at cox.net>
Signed-off-by: Junio C Hamano <junkio@cox.net>
#!/bin/sh
. git-sh-setup || die "Not a git archive"
+usage () {
+ die "Usage: git push [--all] [--force] <repository> [<refspec>]"
+}
+
+
# Parse out parameters and then stop at remote, so that we can
# translate it using .git/branches information
has_all=
--exec=*)
has_exec="$1" ;;
-*)
- die "Unknown parameter $1" ;;
+ usage ;;
*)
set x "$@"
shift
shift
case "$remote" in
-http://* | https://* | git://* | rsync://* )
- die "Cannot push to $remote" ;;
+http://* | https://* | git://*)
+ die "Cannot use READ-ONLY transport to push to $remote" ;;
+rsync://*)
+ die "Pushing with rsync transport is deprecated" ;;
esac
set x "$remote" "$@"; shift