git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] document --exec for git-push

From
Uwe Kleine-König <zeisberg@informatik.uni-freiburg.de>
Date
Jan 16, 2007, 15:02 UTC
Message-ID
<20070116150201.GA2427@cepheus>
The text is just copied from git-send-pack.txt.
Signed-off-by: Uwe Kleine-König <zeisberg@informatik.uni-freiburg.de>
---
 Documentation/git-push.txt |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

There are still some options undocumented, but I don't know what they do exacly:

	--thin
	--no-thin
	--repo=
	-v
(OK, I just now saw -v and I'm to lazy to do it now :-)

Best regards Uwe

diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 197f4b5..a19631d 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -8,7 +8,7 @@ git-push - Update remote refs along with associated objects
 
 SYNOPSIS
 --------
-'git-push' [--all] [--tags] [-f | --force] <repository> <refspec>...
+'git-push' [--all] [--tags] [--exec=<receive-pack>] [-f | --force] <repository> <refspec>...
 
 DESCRIPTION
 -----------
@@ -67,6 +67,12 @@ the remote repository.
 	addition to refspecs explicitly listed on the command
 	line.
 
+\--exec::
+	Path to the 'git-receive-pack' program on the remote
+	end.  Sometimes useful when pushing to a remote
+	repository over ssh, and you do not have the program in
+	a directory on the default $PATH.
+
 -f, \--force::
 	Usually, the command refuses to update a remote ref that is
 	not a descendant of the local ref used to overwrite it.
-- 
1.5.0.rc1.g581a

-- 
Uwe Kleine-König

http://www.google.com/search?q=72+PS+point+in+inch
Next: Junio C Hamano
Message 1 of 2 in “document --exec for git-push”
  1. document --exec for git-pushUwe Kleine-König, Jan 16, 2007
  2. Junio C HamanoJan 16, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.