undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make it clear that push can take multiple refspecs

Browse Source 
Signed-off-by: Abhijit Menon-Sen <ams@toroid.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Abhijit Menon-Sen 2008-07-30 04:43:38 +05:30 committed by Junio C Hamano
parent a56bf5850a
commit 2c9693bda5
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Documentation/git-push.txt
View File

@ -10,7 +10,8 @@ SYNOPSIS
-------- --------
[verse] [verse]
'git push' [--all] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>] 'git push' [--all] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>]
[--repo=all] [-f | --force] [-v | --verbose] [<repository> <refspec>...] [--repo=all] [-f | --force] [-v | --verbose]
[<repository> <refspec>...]
DESCRIPTION DESCRIPTION
----------- -----------
@ -29,8 +30,8 @@ OPTIONS
The "remote" repository that is destination of a push The "remote" repository that is destination of a push
operation. See the section <<URLS,GIT URLS>> below. operation. See the section <<URLS,GIT URLS>> below.
<refspec>:: <refspec>...::
The canonical format of a <refspec> parameter is The canonical format of each <refspec> parameter is
`+?<src>:<dst>`; that is, an optional plus `+`, followed `+?<src>:<dst>`; that is, an optional plus `+`, followed
by the source ref, followed by a colon `:`, followed by by the source ref, followed by a colon `:`, followed by
the destination ref. the destination ref.
@ -180,11 +181,11 @@ git push origin :experimental::
Find a ref that matches `experimental` in the `origin` repository Find a ref that matches `experimental` in the `origin` repository
(e.g. `refs/heads/experimental`), and delete it. (e.g. `refs/heads/experimental`), and delete it.
git push origin master:satellite/master:: git push origin master:satellite/master dev:satellite/dev::
Find a ref that matches `master` in the source repository Use the source ref that matches `master` (e.g. `refs/heads/master`)
(most likely, it would find `refs/heads/master`), and update to update the ref that matches `satellite/master` (most probably
the ref that matches `satellite/master` (most likely, it would `refs/remotes/satellite/master`) in the `origin` repository, then
be `refs/remotes/satellite/master`) in `origin` repository with it. do the same for `dev` and `satellite/dev`.
git push origin master:refs/heads/experimental:: git push origin master:refs/heads/experimental::
Create the branch `experimental` in the `origin` repository Create the branch `experimental` in the `origin` repository