mirror of
https://github.com/git/git
synced 2024-08-27 11:39:22 +00:00
user-manual: Update for receive.denyCurrentBranch=refuse
acd2a45
(Refuse updating the current branch in a non-bare repository via push, 2009-02-11) changed the default to refuse such a push, but it forgot to update the docs.7d182f5
(Documentation: receive.denyCurrentBranch defaults to 'refuse', 2010-03-17) updated Documentation/config.txt, but forgot to update the user manual. Signed-off-by: W. Trevor King <wking@tremily.us> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
7e2010537e
commit
d9be2485e2
|
@ -1986,9 +1986,10 @@ handling this case.
|
||||||
|
|
||||||
Note that the target of a "push" is normally a
|
Note that the target of a "push" is normally a
|
||||||
<<def_bare_repository,bare>> repository. You can also push to a
|
<<def_bare_repository,bare>> repository. You can also push to a
|
||||||
repository that has a checked-out working tree, but the working tree
|
repository that has a checked-out working tree, but a push to update the
|
||||||
will not be updated by the push. This may lead to unexpected results if
|
currently checked-out branch is denied by default to prevent confusion.
|
||||||
the branch you push to is the currently checked-out branch!
|
See the description ofthe receive.denyCurrentBranch option
|
||||||
|
in linkgit:git-config[1] for details.
|
||||||
|
|
||||||
As with `git fetch`, you may also set up configuration options to
|
As with `git fetch`, you may also set up configuration options to
|
||||||
save typing; so, for example, after
|
save typing; so, for example, after
|
||||||
|
|
Loading…
Reference in a new issue