From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] update-hook: remove all functionality that should be in hooks/post-receive
Date: Sat, 24 Mar 2007 10:21:04 -0400 [thread overview]
Message-ID: <20070324142104.GA31791@thunk.org> (raw)
In-Reply-To: <7vodmikjol.fsf@assigned-by-dhcp.cox.net>
On Sat, Mar 24, 2007 at 03:41:30AM -0700, Junio C Hamano wrote:
> While I think it would be great to have a central clearinghouse
> for people to share and enjoy useful hook collections for
> various workflows and use cases, I do not necessarily think
> inside git.git project itself is the best place to do so.
What are your concernswith having a set of useful hook collections in
contrib/hooks, which get installed in /usr/share/git/hooks, or some
such? The nice of doing this is that various distro packages will
have the hooks installed in standardized places, which means that it
becomes easier for people distribute receipes on how to enable various
advanced bits of functionality by using 'ln -s /usr/share/git/hooks/FOO
.git/hooks/BAR', and it's standardized across distributions.
- Ted
next prev parent reply other threads:[~2007-03-24 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 10:21 [PATCH] update-hook: remove all functionality that should be in hooks/post-receive Andy Parkins
2007-03-24 1:09 ` Junio C Hamano
2007-03-24 3:23 ` Linus Torvalds
2007-03-24 3:28 ` Shawn O. Pearce
2007-03-24 8:14 ` Andy Parkins
2007-03-24 10:26 ` Theodore Tso
2007-03-24 10:41 ` Junio C Hamano
2007-03-24 12:44 ` Andy Parkins
2007-03-24 14:21 ` Theodore Tso [this message]
2007-03-24 14:43 ` Francis Moreau
2007-03-24 15:48 ` Andy Parkins
2007-03-24 18:15 ` Francis Moreau
2007-03-25 9:11 ` Andy Parkins
2007-03-25 9:25 ` Shawn O. Pearce
2007-03-25 14:04 ` Francis Moreau
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=20070324142104.GA31791@thunk.org \
--to=tytso@mit.edu \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).