Make it clear that push can take multiple refspecs
Signed-off-by: Abhijit Menon-Sen <ams@toroid.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Abhijit Menon-Sen committed
Jul 30, 2008 at 04:43 UTC
2c9693bda5f5c726847b4763dd6f82cfdca3e8d7
1 file changed
+9
-8
Documentation/git-push.txt
+9
-8
@@ -10,7 +10,8 @@ SYNOPSIS
10
--------
11
[verse]
12
'git push' [--all] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>]
13
- [--repo=all] [-f | --force] [-v | --verbose] [<repository> <refspec>...]
13
+ [--repo=all] [-f | --force] [-v | --verbose]
14
+ [<repository> <refspec>...]
15
16
DESCRIPTION
17
-----------
@@ -29,8 +30,8 @@ OPTIONS
30
The "remote" repository that is destination of a push
31
operation. See the section <<URLS,GIT URLS>> below.
32
32
-<refspec>::
33
- The canonical format of a <refspec> parameter is
33
+<refspec>...::
34
+ The canonical format of each <refspec> parameter is
35
`+?<src>:<dst>`; that is, an optional plus `+`, followed
36
by the source ref, followed by a colon `:`, followed by
37
the destination ref.
@@ -180,11 +181,11 @@ git push origin :experimental::
181
Find a ref that matches `experimental` in the `origin` repository
182
(e.g. `refs/heads/experimental`), and delete it.
183
183
-git push origin master:satellite/master::
184
- Find a ref that matches `master` in the source repository
185
- (most likely, it would find `refs/heads/master`), and update
186
- the ref that matches `satellite/master` (most likely, it would
187
- be `refs/remotes/satellite/master`) in `origin` repository with it.
184
+git push origin master:satellite/master dev:satellite/dev::
185
+ Use the source ref that matches `master` (e.g. `refs/heads/master`)
186
+ to update the ref that matches `satellite/master` (most probably
187
+ `refs/remotes/satellite/master`) in the `origin` repository, then
188
+ do the same for `dev` and `satellite/dev`.
189
190
git push origin master:refs/heads/experimental::
191
Create the branch `experimental` in the `origin` repository