git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Marlene Cote <Marlene_Cote@affirmednetworks.com>, git@vger.kernel.org
Subject: shared hooks (Re: help for a git newbie please)
Date: Wed, 29 Dec 2010 13:17:17 -0600	[thread overview]
Message-ID: <20101229191717.GA19195@burratino> (raw)
In-Reply-To: <m3k4iscsq2.fsf@localhost.localdomain>

Jakub Narebski wrote:

> Now, if you either use some kind of networked filesystem, or you can
> configure it so each developers machine has the same install, you can
> make use of git templates mechanism.

To expand on this: if you are in the "controlled environment"
situation, you may find the discussion pointed to by [1] interesting.

If you do not control developer machines, life is even simpler.
One approach[2] is to track a git-templates/ directory in the working
tree and add a setup-hooks.sh script that installs those hooks in
.git/hooks.

[1] http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/776932
Summary: it is easier to change hooks later if you keep hooks in some
directory outside the template dir (e.g., in /etc/hooks) and put a
symlink to that directory in the template.
[2] e.g., used by the libreoffice repository iirc

  reply	other threads:[~2010-12-29 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 17:43 help for a git newbie please Marlene Cote
2010-12-29 18:58 ` Jakub Narebski
2010-12-29 19:17   ` Jonathan Nieder [this message]
2010-12-29 19:26   ` help for a git newbie please - git hooks Marlene Cote

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=20101229191717.GA19195@burratino \
    --to=jrnieder@gmail.com \
    --cc=Marlene_Cote@affirmednetworks.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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 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 NNTP newsgroup(s).