Git development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add support in sample hook script for denying annotated tags.
Date: Sun, 31 Oct 2010 15:24:33 -0500	[thread overview]
Message-ID: <20101031202433.GB21240@burratino> (raw)
In-Reply-To: <201010311457.17817.bss@iguanasuicide.net>

Hi,

Boyd Stephen Smith Jr. wrote:

> Signed-off-by: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
> ---
>  templates/hooks--update.sample |    9 +++++++++
>  1 files changed, 9 insertions(+), 0 deletions(-)
> 
> In one project I'm in we are using a centralized Git repository that many 
> developers have access to.  As such, we want to prevent tags from being 
> created by push operations and have them created by the administrators.
> 
> This is a modification to the sample update hook to allow this to simply be 
> a configuration option.

This kind of justification belongs above the "---", I think.

No opinion on the functionality itself.  Just:

> --- a/templates/hooks--update.sample
> +++ b/templates/hooks--update.sample
> @@ -7,6 +7,9 @@
>  #
>  # Config
>  # ------
> +# hooks.allowannotated
> +#   This boolean sets whether annotated tags will be allowed into the
> +#   repository.  By default they won't be.

hooks.denyannotated (defaulting to false) would be more consistent
with hooks.denycreatebranch, no?

Or maybe hooks.denycreatetag --- a situation in which unannotated
tags should be allowed but annotated denied seems hard to imagine.

Hope that helps,
Jonathan

  reply	other threads:[~2010-10-31 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 19:57 [PATCH] Add support in sample hook script for denying annotated tags Boyd Stephen Smith Jr.
2010-10-31 20:24 ` Jonathan Nieder [this message]
2010-11-01  7:29   ` Boyd Stephen Smith Jr.

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=20101031202433.GB21240@burratino \
    --to=jrnieder@gmail.com \
    --cc=bss@iguanasuicide.net \
    --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