git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: demerphq <demerphq@gmail.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.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 11:32:35 -0400	[thread overview]
Message-ID: <AANLkTik-CHI2D4HYn1T2ExsyE7G3kKX4LwHf0eQRrfP1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinCFP18B8PQoGREt-izxGSlUb3IzitxK4aeiFRD@mail.gmail.com>

> 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
>

I suppose the default configuration is not suggesting any system or
global level hooks folders defined in proposed solution. If some admin
or SCM makes a decision about system level hooks - he has to know what
he's doing - that's is pretty much it. But it might be very
comfortable way to set up some rules or enforce policies.
OTOH user level (--global) hooks are going to be responsible for what
user does all the time and wants to automate.


Thanks,
Eugene

  reply	other threads:[~2010-07-06 15:32 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
2010-07-06 15:32               ` Eugene Sajine [this message]
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=AANLkTik-CHI2D4HYn1T2ExsyE7G3kKX4LwHf0eQRrfP1@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=demerphq@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).