From: "Uwe Kleine-König" <zeisberg@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: [PATCH] document --exec for git-push
Date: Tue, 16 Jan 2007 16:02:02 +0100 [thread overview]
Message-ID: <20070116150201.GA2427@cepheus> (raw)
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 reply other threads:[~2007-01-16 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 15:02 Uwe Kleine-König [this message]
2007-01-16 19:45 ` [PATCH] document --exec for git-push Junio C Hamano
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=20070116150201.GA2427@cepheus \
--to=zeisberg@informatik.uni-freiburg.de \
--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.