From: c.shoemaker@cox.net
To: unlisted-recipients:; (no To-header on input)
Subject: [PATCH] Add usage statement to git-push.sh
Date: Sat, 29 Oct 2005 00:16:33 -0400 [thread overview]
Message-ID: <E1EVi8v-0002To-Qx@localhost> (raw)
Also clarify failure to push to read-only remote.
Signed-off-by: Chris Shoemaker <c.shoemaker at cox.net>
---
git-push.sh | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
c312de8ed8aad08a3cfa4b8edce025f30781a1c3
diff --git a/git-push.sh b/git-push.sh
--- a/git-push.sh
+++ b/git-push.sh
@@ -18,7 +18,8 @@ do
--exec=*)
has_exec="$1" ;;
-*)
- die "Unknown parameter $1" ;;
+ die "Usage: git push [--all] [--force] <repository> <refspec>"
+ ;;
*)
set x "$@"
shift
@@ -41,7 +42,7 @@ shift
case "$remote" in
http://* | https://* | git://* | rsync://* )
- die "Cannot push to $remote" ;;
+ die "Cannot use READ-ONLY transport to push to $remote" ;;
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=E1EVi8v-0002To-Qx@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 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).