[PATCH] receive.txt: Describe effect of denyDeleteCurrent on bare repositories

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The receive.denyDeleteCurrent config option not only affects non-bare
repositories, but also the default branch of a bare repository.

Signed-off-by: Andreas Schwab <schwab@xxxxxxx>
---
 Documentation/config/receive.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/config/receive.txt b/Documentation/config/receive.txt
index 85d5b5a3d2..07db745cd4 100644
--- a/Documentation/config/receive.txt
+++ b/Documentation/config/receive.txt
@@ -80,7 +80,8 @@ receive.denyDeletes::
 
 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.
+	deletes the currently checked out branch of a non-bare repository,
+	or the default branch of a bare repository.
 
 receive.denyCurrentBranch::
 	If set to true or "refuse", git-receive-pack will deny a ref update
-- 
2.37.3


-- 
Andreas Schwab, SUSE Labs, schwab@xxxxxxx
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux