Re: global hooks - once again

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6 July 2010 16:55, Peter Kjellerstedt <peter.kjellerstedt@xxxxxxxx> wrote:
>> -----Original Message-----
>> From: git-owner@xxxxxxxxxxxxxxx [mailto:git-owner@xxxxxxxxxxxxxxx] On
>> Behalf Of Eugene Sajine
>> Sent: den 6 juli 2010 14:23
>> To: Alex Riesen
>> Cc: git@xxxxxxxxxxxxxxx
>> 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/"
--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]