From: c.shoemaker@cox.net
To: unlisted-recipients:; (no To-header on input)
Subject: [PATCH] git-push.sh: Factor out usage statement to function; explain why rsync can't push
Date: Sat, 29 Oct 2005 00:17:03 -0400 [thread overview]
Message-ID: <E1EVi9P-0002Tw-BD@localhost> (raw)
Signed-off-by: Chris Shoemaker <c.shoemaker at cox.net>
---
git-push.sh | 12 +++++++++---
1 files changed, 9 insertions(+), 3 deletions(-)
cc2f6f361691771cf461df04255a2b842b264371
diff --git a/git-push.sh b/git-push.sh
--- a/git-push.sh
+++ b/git-push.sh
@@ -1,6 +1,11 @@
#!/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=
@@ -18,8 +23,7 @@ do
--exec=*)
has_exec="$1" ;;
-*)
- die "Usage: git push [--all] [--force] <repository> <refspec>"
- ;;
+ usage ;;
*)
set x "$@"
shift
@@ -41,8 +45,10 @@ esac
shift
case "$remote" in
-http://* | https://* | git://* | rsync://* )
+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
reply other threads:[~2005-10-29 4:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1EVi9P-0002Tw-BD@localhost \
--to=c.shoemaker@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.