From: Miklos Vajna <vmiklos@frugalware.org>
To: Thomas Hunger <hto@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: multiple files for the same hook
Date: Mon, 12 May 2008 22:44:45 +0200 [thread overview]
Message-ID: <20080512204445.GT27724@genesis.frugalware.org> (raw)
In-Reply-To: <200805122039.49779.hto@arcor.de>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Mon, May 12, 2008 at 08:39:49PM +0000, Thomas Hunger <hto@arcor.de> wrote:
> we use hooks a lot for various cleanup tasks, tests and warnings. It
> would be wonderful if we could keep the hook logic in separate files.
>
> Something like
>
> hooks/post-commit.d/
>
> where all executable files in the dir are executed in alphanumeric
> order. Is there a possibility of this going into git (I could try a
> patch)?
why would you want so? just create a script named hooks/post-commit,
like:
----
#!/bin/sh
/path/to/first/script
/path/to/second/script
----
or so.
it's not something git should do for you.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-12 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 20:39 multiple files for the same hook Thomas Hunger
2008-05-12 20:43 ` Sverre Rabbelier
2008-05-12 20:44 ` Miklos Vajna [this message]
2008-05-12 21:56 ` Thomas Hunger
2008-05-13 4:21 ` Jeff King
2008-05-13 8:05 ` Martin Langhoff
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=20080512204445.GT27724@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=hto@arcor.de \
/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