From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: [PATCH 2/2] Add support for git-http-push to git-push script
Date: Wed, 2 Nov 2005 11:19:31 -0800 [thread overview]
Message-ID: <20051102191930.GD3928@reactrix.com> (raw)
Add support for git-http-push to git-push script
Signed-off-by: Nick Hengeveld <nickh@reactrix.com>
---
This probably doesn't make sense until git-http-push has undergone some
testing.
git-push.sh | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
applies-to: e7d656bb2608ae924a78750bbd3d01bf4f6c2e9a
a374b962104899cfe39b21fc2fbef64d1e1fdbd8
diff --git a/git-push.sh b/git-push.sh
index 5aa6531..edc0b83 100755
--- a/git-push.sh
+++ b/git-push.sh
@@ -46,7 +46,7 @@ esac
shift
case "$remote" in
-http://* | https://* | git://*)
+git://*)
die "Cannot use READ-ONLY transport to push to $remote" ;;
rsync://*)
die "Pushing with rsync transport is deprecated" ;;
@@ -57,4 +57,9 @@ test "$has_all" && set x "$has_all" "$@"
test "$has_force" && set x "$has_force" "$@" && shift
test "$has_exec" && set x "$has_exec" "$@" && shift
-exec git-send-pack "$@"
+case "$remote" in
+http://* | https://*)
+ exec git-http-push "$@";;
+*)
+ exec git-send-pack "$@";;
+esac
---
0.99.9.GIT
reply other threads:[~2005-11-02 19:19 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=20051102191930.GD3928@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
/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.