[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <xmqqa9hp9x2e.fsf@gitster.dls.corp.google.com>
Date: Thu, 31 Oct 2013 10:20:25 -0700
From: Junio C Hamano <gitster@...ox.com>
To: Duy Nguyen <pclouds@...il.com>
Cc: Johan Herland <johan@...land.net>, Jeff King <peff@...f.net>,
Michael Haggerty <mhagger@...m.mit.edu>,
Josh Triplett <josh@...htriplett.org>,
Git mailing list <git@...r.kernel.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
Greg KH <greg@...ah.com>,
Linux Kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] commit: Add -f, --fixes <commit> option to add Fixes: line
Duy Nguyen <pclouds@...il.com> writes:
> OK how about, if $GIT_DIR/hooks/something is a directory, then the
> directory must contain a file named "index", listing all the hooks of
> type "something". All the hooks in "index" will be executed in the
> listing order.
Hooks that take arbitrary amount of information from the body read
their standard input. How are your multiple hooks supposed to
interact?
Hooks that prevent you from doing something stupid signal allow/deny
with their exit code. Do you fail a commit if any of your pre-commit
hook fails, or is it OK to commit as long as one of them says so?
If the former, do all the hooks described in the index still run, or
does the first failure short-cut the remainder?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists