From: Jonathan Nieder <jrnieder@gmail.com>
To: Chris Patti <cpatti@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Example git hooks (Re: Odd results writing a Git pre-receive hook to syntax check PHP files.)
Date: Mon, 30 Aug 2010 09:34:11 -0500 [thread overview]
Message-ID: <20100830143411.GH2315@burratino> (raw)
In-Reply-To: <AANLkTi=GUrnH87faWH8G0tD7_KAynVf_ig0KpQRwnsaE@mail.gmail.com>
Chris Patti wrote:
> (P.S. Is there a canonical 'example Git hooks' location I could
> publish this to when it's working? I think there's a dearth of this
> kind of example for people out there right now)
Try the git wiki (git.wiki.kernel.org). There is a page for aliases
but no page for example hooks yet (though there are some examples
under InterfacesFrontendsAndTools). You could be the trailblazer.
There are also a few examples in git templates/ and contrib/hooks,
of course.
next prev parent reply other threads:[~2010-08-30 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 21:07 Odd results writing a Git pre-receive hook to syntax check PHP files Chris Patti
2010-08-30 10:55 ` Michael J Gruber
2010-08-30 14:03 ` Chris Patti
2010-08-30 14:16 ` Jonathan Nieder
2010-08-30 14:24 ` Chris Patti
2010-08-30 14:34 ` Jonathan Nieder [this message]
2010-08-31 1:57 ` Example git hooks (Re: Odd results writing a Git pre-receive hook to syntax check PHP files.) Todd Zullinger
2010-08-31 13:11 ` Chris Patti
2010-08-31 21:14 ` Chris Patti
2010-08-30 14:30 ` Odd results writing a Git pre-receive hook to syntax check PHP files Michael J Gruber
2010-08-30 15:00 ` Chris Patti
2010-08-30 16:27 ` Chris Patti
2010-08-30 16:32 ` Sverre Rabbelier
2010-08-30 16:33 ` Jonathan Nieder
2010-08-30 17:37 ` Chris Patti
2010-08-30 19:10 ` Michael J Gruber
2010-08-31 21:06 ` Chris Patti
2010-08-31 23:50 ` Junio C Hamano
2010-09-01 13:43 ` Chris Patti
2010-09-02 14:34 ` Chris Patti
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=20100830143411.GH2315@burratino \
--to=jrnieder@gmail.com \
--cc=cpatti@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/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).