All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Brian Vandenberg <phantall@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] [RFC] Make git-update-ref invoke the update and post-update hooks
Date: Mon, 15 Jun 2015 14:45:55 -0700	[thread overview]
Message-ID: <xmqqd20w7ii4.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAEJ-0i8mfabWoLivX_ZJHRJBYFftoENWmHw5__CGphK54oOpug@mail.gmail.com> (Brian Vandenberg's message of "Mon, 15 Jun 2015 14:58:35 -0600")

Brian Vandenberg <phantall@gmail.com> writes:

> Would you be less doubtful about adding a lower-level hook for
> update-ref?  Or in lieu of that, a config option that can affect the
> behavior of its "-m" and "-d" options?

Not really.

Those who want to bypass your policy can use "vi .git/packed-refs"
and/or "rm .git/refs/heads/foo"; you would not propose to patch "rm"
and "vi" to pay attention to git configuration, because they are not
about "git" at all, and there are cases where these bare-metal level
editing of repositories is necessary.  You would instead tell them
"don't do that".

When I say "update-ref is a low-level plumbing command that should
not enforce policy", I am suggesting you to treat the command just
like you would treat "rm" and "vi".

  reply	other threads:[~2015-06-15 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 19:49 [PATCH] [RFC] Make git-update-ref invoke the update and post-update hooks Brian Vandenberg
2015-06-15 20:22 ` Junio C Hamano
2015-06-15 20:58   ` Brian Vandenberg
2015-06-15 21:45     ` Junio C Hamano [this message]
2015-06-16 14:31       ` Brian Vandenberg
  -- strict thread matches above, loose matches on Subject: below --
2006-10-08  0:08 Petr Baudis
2006-10-08  5:00 ` Junio C Hamano

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=xmqqd20w7ii4.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=phantall@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.