git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] update-hook: remove all functionality that should be in hooks/post-receive

From
Theodore Tso <tytso@mit.edu>
Date
Mar 24, 2007, 14:21 UTC
Message-ID
<20070324142104.GA31791@thunk.org>
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
Previous: Andy ParkinsNext: Francis Moreau
Message 9 of 15 in “update-hook: remove all functionality that should be in hooks/post-receive”
  1. update-hook: remove all functionality that should be in hooks/post-receiveAndy Parkins, Mar 23, 2007
  2. Junio C HamanoMar 24, 2007
  3. Linus TorvaldsMar 24, 2007
  4. Shawn O. PearceMar 24, 2007
  5. Andy ParkinsMar 24, 2007
  6. Theodore TsoMar 24, 2007
  7. Junio C HamanoMar 24, 2007
  8. Andy ParkinsMar 24, 2007
  9. Theodore TsoMar 24, 2007
  10. Francis MoreauMar 24, 2007
  11. Andy ParkinsMar 24, 2007
  12. Francis MoreauMar 24, 2007
  13. Andy ParkinsMar 25, 2007
  14. Shawn O. PearceMar 25, 2007
  15. Francis MoreauMar 25, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.