summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-09-09 04:35:53 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-09-09 04:35:53 (GMT)
commitf34d900aa7346592a9d7fd2eb7b21126fd9732d5 (patch)
treebf756b15988b94b1f045a6f53c1eec9c3c479812 /Documentation
parentf59c6e6ccb1386f0fdde2753f62536dfd3343118 (diff)
parent9eed4f3711a605ab2d9b986357879a09a6d54f36 (diff)
downloadgit-f34d900aa7346592a9d7fd2eb7b21126fd9732d5.zip
git-f34d900aa7346592a9d7fd2eb7b21126fd9732d5.tar.gz
git-f34d900aa7346592a9d7fd2eb7b21126fd9732d5.tar.bz2
Merge branch 'jk/push-force-with-lease-creation' into maint
"git push --force-with-lease" already had enough logic to allow ensuring that such a push results in creation of a ref (i.e. the receiving end did not have another push from sideways that would be discarded by our force-pushing), but didn't expose this possibility to the users. It does so now. * jk/push-force-with-lease-creation: t5533: make it pass on case-sensitive filesystems push: allow pushing new branches with --force-with-lease push: add shorthand for --force-with-lease branch creation Documentation/git-push: fix placeholder formatting
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-push.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 93c3527..927a034 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -198,10 +198,11 @@ branch we have for it.
+
`--force-with-lease=<refname>:<expect>` will protect the named ref (alone),
if it is going to be updated, by requiring its current value to be
-the same as the specified value <expect> (which is allowed to be
+the same as the specified value `<expect>` (which is allowed to be
different from the remote-tracking branch we have for the refname,
or we do not even have to have such a remote-tracking branch when
-this form is used).
+this form is used). If `<expect>` is the empty string, then the named ref
+must not already exist.
+
Note that all forms other than `--force-with-lease=<refname>:<expect>`
that specifies the expected current value of the ref explicitly are