summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-09-19 18:38:31 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-09-19 18:38:31 (GMT)
commitd9dd4cebec3107545b4354a198ecbc5a141f3f46 (patch)
tree49ee55d74f5347393359b2e4335309304268388b /Documentation
parent30d45f798d1a4b14759cd977b68be4476d66ea17 (diff)
parent26be19ba8d8d2e7e3e288b395e7156d5b7af5140 (diff)
downloadgit-d9dd4cebec3107545b4354a198ecbc5a141f3f46.zip
git-d9dd4cebec3107545b4354a198ecbc5a141f3f46.tar.gz
git-d9dd4cebec3107545b4354a198ecbc5a141f3f46.tar.bz2
Merge branch 'jk/send-pack-many-refspecs'
The number of refs that can be pushed at once over smart HTTP was limited by the command line length. The limitation has been lifted by passing these refs from the standard input of send-pack. * jk/send-pack-many-refspecs: send-pack: take refspecs over stdin
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-send-pack.txt13
1 files changed, 12 insertions, 1 deletions
diff --git a/Documentation/git-send-pack.txt b/Documentation/git-send-pack.txt
index dc3a568..2a0de42 100644
--- a/Documentation/git-send-pack.txt
+++ b/Documentation/git-send-pack.txt
@@ -35,6 +35,16 @@ OPTIONS
Instead of explicitly specifying which refs to update,
update all heads that locally exist.
+--stdin::
+ Take the list of refs from stdin, one per line. If there
+ are refs specified on the command line in addition to this
+ option, then the refs from stdin are processed after those
+ on the command line.
++
+If '--stateless-rpc' is specified together with this option then
+the list of refs must be in packet format (pkt-line). Each ref must
+be in a separate packet, and the list must end with a flush packet.
+
--dry-run::
Do everything except actually send the updates.
@@ -77,7 +87,8 @@ this flag.
Without '--all' and without any '<ref>', the heads that exist
both on the local side and on the remote side are updated.
-When one or more '<ref>' are specified explicitly, it can be either a
+When one or more '<ref>' are specified explicitly (whether on the
+command line or via `--stdin`), it can be either a
single pattern, or a pair of such pattern separated by a colon
":" (this means that a ref name cannot have a colon in it). A
single pattern '<name>' is just a shorthand for '<name>:<name>'.