Re: [PATCH RFC] new config option remote.<name>.pushexec

From: Junio C Hamano <junkio@cox.net>
Date: Jan 17, 2007, 17:32 UTC
Message-ID: <7vps9dsgn0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070117164410.GA5950@cepheus>

Uwe Kleine-König  <zeisberg@informatik.uni-freiburg.de> writes:

> I tried to do the symmetric part for fetch, but that shell script is too
> complicated for me and so I let this part to s.o. being more familiar
> with git-fetch.sh.

I do not know what s.o. is but something like this untested patch would do.

I do not have strong objection to the configuration on the push side, but I am not sure if we want to call it pushexec -- it is naming receive-pack so remote.*.receivepack might be more appropriate, just in case we update the fetch/push protocol someday to run more than one program on the other end.

diff --git a/git-fetch.sh b/git-fetch.sh
index 87b940b..7372c5f 100755
--- a/git-fetch.sh
+++ b/git-fetch.sh
@@ -82,6 +82,13 @@ case "$#" in
 	set x $origin ; shift ;;
 esac
 
+if test -z "$exec" && exec=$(git-repo-config "remote.$1.uploadpack")
+then
+	# No command line override and we have configuration for the remote.
+	upload_pack="-u $exec"
+	exec="--exec=$exec"
+fi
+
 remote_nick="$1"
 remote=$(get_remote_url "$@")
 refs=