[PATCH v1.1 1/2] Document receive.denyDeleteCurrent
- From
Thomas Rast <trast@student.ethz.ch>
- Date
- Jul 24, 2010, 16:07 UTC
- Message-ID
- <ab7b73ce593846b083bf0f4c4c7de08fb6008a5e.1279987608.git.trast@student.ethz.ch>
- In-Reply-To
- <ab7b73ce593846b083bf0f4c4c7de08fb6008a5e.1279986834.git.trast@student.ethz.ch>
This option was introduced by 747ca24 (receive-pack: receive.denyDeleteCurrent, 2009-02-08) but never documented.
Signed-off-by: Thomas Rast <trast@student.ethz.ch> ---
Argh, there was a typo ("receive,pack") in the first version. Why do I only notice them on the 4th reading. Sorry for the noise.
Documentation/config.txt | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index e75434b..fdb90c0 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -1558,6 +1558,10 @@ receive.denyDeletes:: If set to true, git-receive-pack will deny a ref update that deletes 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. + receive.denyCurrentBranch:: If set to true or "refuse", git-receive-pack will deny a ref update to the currently checked out branch of a non-bare repository.
-- 1.7.2.278.g76edd.dirty