Introduce receive.denyDeletes
authorJan Krüger <jk@jk.gs>
Sat, 1 Nov 2008 14:42:16 +0000 (15:42 +0100)
committerJunio C Hamano <gitster@pobox.com>
Sun, 2 Nov 2008 08:54:28 +0000 (01:54 -0700)
commita240de1137bd63a969c6bd56ab5186d7216e28ca
tree6a876638cfc09ee414599b0d4dae46eca7b10105
parentaebd173ffa7a4e67447f0157a14abde7767c54e9
Introduce receive.denyDeletes

Occasionally, it may be useful to prevent branches from getting deleted from
a centralized repository, particularly when no administrative access to the
server is available to undo it via reflog. It also makes
receive.denyNonFastForwards more useful if it is used for access control
since it prevents force-updating by deleting and re-creating a ref.

Signed-off-by: Jan Krüger <jk@jk.gs>
Acked-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/config.txt
builtin-receive-pack.c
t/t5400-send-pack.sh