[PATCH] Documentation/config.txt: denyDeleteCurrent applies to bare repos too
- From
- Brandon Casey <bcasey@nvidia.com>
- Date
- Oct 16, 2013, 01:26 UTC
- Message-ID
- <1381886818-14337-1-git-send-email-bcasey@nvidia.com>
From: Brandon Casey <drafnel@gmail.com>
The setting of denyDeleteCurrent applies to both bare and non-bare repositories. Correct the description on this point, and expand it to provide some background justification for the current behavior and describe the full suite of settings.
Signed-off-by: Brandon Casey <drafnel@gmail.com> --- Documentation/config.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index c3f7002..3d416ec 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -1993,8 +1993,15 @@ receive.denyDeletes:: the ref. Use this to prevent such a ref deletion via a push. receive.denyDeleteCurrent:: - If set to true, git-receive-pack will deny a ref update that - deletes the currently checked out branch of a non-bare repository. + If set to true or "refuse", git-receive-pack will deny a ref update + that deletes the currently checked out branch of a non-bare repository, + or the "default" branch in a bare repository. i.e. the branch + that HEAD refers to. Deleting the current branch from a remote will + cause the HEAD symbolic ref to become dangling and will result in the + next clone from it to not check out anything. If set to "warn", + then a warning will be printed to stderr and the deletion will be + performed. If set to false or "ignore", then the deletion will be + performed with no warning message. Defaults to "refuse". receive.denyCurrentBranch:: If set to true or "refuse", git-receive-pack will deny a ref update
-- 1.8.4.rc4.6.g5555d19 ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------