diff options
| author | Junio C Hamano <gitster@pobox.com> | 2015-02-17 14:11:26 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2015-02-17 14:11:26 -0800 |
| commit | 6bb32e61faff1d96d84d668f44b4440210b0e23c (patch) | |
| tree | aea24c30b07a7bfb8869945bba6a5d75701cc1c4 /git-push.txt | |
| parent | 0bcc239ed214940dcb68139f571d91bf04f1a0c9 (diff) | |
| download | git-htmldocs-6bb32e61faff1d96d84d668f44b4440210b0e23c.tar.gz | |
Autogenerated HTML docs for v2.3.0-130-g3188a
Diffstat (limited to 'git-push.txt')
| -rw-r--r-- | git-push.txt | 25 |
1 files changed, 8 insertions, 17 deletions
diff --git a/git-push.txt b/git-push.txt index b17283ab7..e1a46a795 100644 --- a/git-push.txt +++ b/git-push.txt @@ -9,7 +9,7 @@ git-push - Update remote refs along with associated objects SYNOPSIS -------- [verse] -'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>] +'git push' [--all | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>] [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream] [--signed] [--force-with-lease[=<refname>[:<expect>]]] @@ -136,6 +136,11 @@ already exists on the remote side. logged. See linkgit:git-receive-pack[1] for the details on the receiving end. +--[no-]atomic:: + Use an atomic transaction on the remote side if available. + Either all refs are updated, or on error, no refs are updated. + If the server does not support atomic pushes the push will fail. + --receive-pack=<git-receive-pack>:: --exec=<git-receive-pack>:: Path to the 'git-receive-pack' program on the remote @@ -214,22 +219,8 @@ origin +master` to force a push to the `master` branch). See the `<refspec>...` section above for details. --repo=<repository>:: - This option is only relevant if no <repository> argument is - passed in the invocation. In this case, 'git push' derives the - remote name from the current branch: If it tracks a remote - branch, then that remote repository is pushed to. Otherwise, - the name "origin" is used. For this latter case, this option - can be used to override the name "origin". In other words, - the difference between these two commands -+ --------------------------- -git push public #1 -git push --repo=public #2 --------------------------- -+ -is that #1 always pushes to "public" whereas #2 pushes to "public" -only if the current branch does not track a remote branch. This is -useful if you write an alias or script around 'git push'. + This option is equivalent to the <repository> argument. If both + are specified, the command-line argument takes precedence. -u:: --set-upstream:: |