[PATCH] user-manual: Update for receive.denyCurrentBranch=refuse
- From
W. Trevor King <wking@tremily.us>
- Date
- Feb 8, 2013, 17:04 UTC
- Message-ID
- <d1f3f900d4886dca727a2176b606e3b76ef9369e.1360343016.git.wking@tremily.us>
From: "W. Trevor King" <wking@tremily.us>
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> --- Documentation/user-manual.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 5077e7c..8e55794 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -1994,8 +1994,10 @@ handling this case. Note that the target of a "push" is normally a <<def_bare_repository,bare>> repository. You can also push to a repository that has a checked-out working tree, but the working tree -will not be updated by the push. This may lead to unexpected results if -the branch you push to is the currently checked-out branch! +will not be updated by the push. To protect against this, pushes to +the currently checked-out branch of a repository are denied by +default. See the description of the receive.denyCurrentBranch option +in linkgit:git-config[1] for details. As with `git fetch`, you may also set up configuration options to save typing; so, for example, after
-- 1.8.1.336.g94702dd