git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: demerphq <demerphq@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Eugene Sajine <euguess@gmail.com>,
	Alex Riesen <raa.lkml@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: global hooks - once again
Date: Tue, 6 Jul 2010 17:00:36 +0200	[thread overview]
Message-ID: <AANLkTinCFP18B8PQoGREt-izxGSlUb3IzitxK4aeiFRD@mail.gmail.com> (raw)
In-Reply-To: <A612847CFE53224C91B23E3A5B48BAC744940F7000@xmail3.se.axis.com>

On 6 July 2010 16:55, Peter Kjellerstedt <peter.kjellerstedt@axis.com> wrote:
>> -----Original Message-----
>> From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On
>> Behalf Of Eugene Sajine
>> Sent: den 6 juli 2010 14:23
>> To: Alex Riesen
>> Cc: git@vger.kernel.org
>> Subject: Re: global hooks - once again
>>
>> > How do your users disable execution of global hooks in this scheme?
>> > (to protect themselves from an evil system administrator)
>
> Yeah, I missed that case. What I have is another configuration
> variable (e.g., core.hooksActiveLevels) which is set to a string of
> different configuration levels (defaulting to 'system global local').
> Only the hook directories specified on an active level are
> scanned for hooks. So by setting it to just 'local' any system
> and global hook directories are ignored.
>
> This is not optimal, but was the best I could come up with.
> I really do not want to force the users to explicitly specify
> the hook directories for each repository, but rather be able
> to set it on a global level, and then use exceptions for the
> few cases where the global hooks should not be active.
>
>> In a corporate environment it is not the case, i believe. If sysadmin
>> made a mistake a with hooks, he will have to fix it, but there is no
>> point in overriding on user level as hooks in this case will be
>> something about company policy, aren't they?
>
> Well, actually it is needed there too. Even though the vast
> majority of repositories the user clones are company repositories
> that should use the company's rules, he may clone some occasional
> repositories from the outside (e.g., Linux or git) in which case
> he probably wants to disable the global company hooks.

Id have guessed that users would be discouraged from having their own
repositories on a central version control server in most larger
environments.

For instance i can imagine that boxes that devs actively work on would
have no global setting, and central version control boxes would have
it.

cheers,
Yves



-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

  reply	other threads:[~2010-07-06 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 16:23 global hooks - once again Eugene Sajine
2010-07-02 18:03 ` Jonathan Nieder
2010-07-02 19:30   ` Eugene Sajine
2010-07-02 19:18 ` Junio C Hamano
2010-07-02 19:47   ` Eugene Sajine
2010-07-05 10:03     ` Peter Kjellerstedt
2010-07-06 12:14       ` Alex Riesen
2010-07-06 12:23         ` Eugene Sajine
2010-07-06 14:55           ` Peter Kjellerstedt
2010-07-06 15:00             ` demerphq [this message]
2010-07-06 15:32               ` Eugene Sajine
2010-07-06 12:20       ` Eugene Sajine
2010-07-06 14:34     ` demerphq
2010-07-02 20:53   ` Jonathan Nieder

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinCFP18B8PQoGREt-izxGSlUb3IzitxK4aeiFRD@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=raa.lkml@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).