From: W. Trevor King Date: Sun, 10 Feb 2013 15:10:28 GMT Subject: [PATCH v2 02/15] user-manual: Update for receive.denyCurrentBranch=refuse Message-ID: In-Reply-To: From: "W. Trevor King" 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 --- 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 222545b..8524c08 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -1988,8 +1988,10 @@ handling this case. Note that the target of a "push" is normally a <> 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