On Mon, May 12, 2008 at 09:56:30PM +0000, Thomas Hunger wrote: > > why would you want so? just create a script named > > hooks/post-commit, like: > > you are right, it's what we actually do, using --template to set up > our own scripts. If nobody but us needs this it's certainly not worth > bothering. The problem is that the semantics of calling some of the hooks is not as simple as just calling them all in a row. How do you split up the input going to the hooks? How do you combine the output coming from the hooks? What is the resulting exit code? If one hook fails, do we indicate failure? Or if one hook succeeds, do we indicate success? So before any such code could go into git proper, there would have to be agreement on how those issues are resolved. In the meantime, it probably makes more sense to implement a "master" post-commit hook that uses the semantics that you find useful. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
