Junio C Hamano <gitster@xxxxxxxxx> writes : > Our documentation can also use some updates, as it dates to the days back > when we more liberally used "refs" and "branches" interchangeably. Ok, I have turned the patch below for documentation. For protecting tags, I can do it with triggers but its painful with lots of repositories. I propose to extend receive.denyDeletes with these values: - "false"/"none" (existing behavior) - "true"/"branches" (existing behavior) - "tags": protect tags only - "all": protect both tags and branches Your opinion ? BR Jérôme Signed-off-by: Jerome de Vivie <jedevivie-ext@xxxxxxxxxxxx> --- Documentation/config.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index 5a841da..9c7c7fe 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -1642,7 +1642,7 @@ receive.unpackLimit:: 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. + a branch. Use this to prevent such a branch deletion via a push. receive.denyDeleteCurrent:: If set to true, git-receive-pack will deny a ref update that -- 1.7.6.msysgit.0 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html