From: Brandon Casey <bcasey@nvidia.com>
To: <git@vger.kernel.org>
Cc: Brandon Casey <drafnel@gmail.com>
Subject: [PATCH] Documentation/config.txt: denyDeleteCurrent applies to bare repos too
Date: Tue, 15 Oct 2013 18:26:58 -0700 [thread overview]
Message-ID: <1381886818-14337-1-git-send-email-bcasey@nvidia.com> (raw)
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.
-----------------------------------------------------------------------------------
next reply other threads:[~2013-10-16 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 1:26 Brandon Casey [this message]
2013-10-17 22:23 ` [PATCH] Documentation/config.txt: denyDeleteCurrent applies to bare repos too Junio C Hamano
2013-10-17 23:29 ` Brandon Casey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1381886818-14337-1-git-send-email-bcasey@nvidia.com \
--to=bcasey@nvidia.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).