Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753654Ab3JaRU3 (ORCPT ); Thu, 31 Oct 2013 13:20:29 -0400 Received: from b-pb-sasl-quonix.pobox.com ([208.72.237.35]:53836 "EHLO smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751353Ab3JaRU2 (ORCPT ); Thu, 31 Oct 2013 13:20:28 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=H9qZ9FKPcdn7Uh7ke9TSHORWBZM9wFkd mdtqMrcpO/dlUX7pPFAqoFnfIJMWYmmymUBwY9CcBLFRBjN4h73bMfEkLVmhL8Xi f4qKJu++NKlONAaJHv6kCtJF6e1IlWpWl3judwcgno7TPKPOj3i9WeR3HpUhknHN 5hIvmn9Oi7A= From: Junio C Hamano To: Duy Nguyen Cc: Johan Herland , Jeff King , Michael Haggerty , Josh Triplett , Git mailing list , Dan Carpenter , Greg KH , Linux Kernel mailing list Subject: Re: [PATCH] commit: Add -f, --fixes option to add Fixes: line References: <20131024122255.GI9378@mwanda> <20131024122512.GB9534@mwanda> <20131026181709.GB10488@kroah.com> <20131027013402.GA7146@leaf> <526CA7D4.1070904@alum.mit.edu> <20131027071407.GA11683@leaf> <526E283A.1070801@alum.mit.edu> <20131029020824.GE11861@sigill.intra.peff.net> Date: Thu, 31 Oct 2013 10:20:25 -0700 In-Reply-To: (Duy Nguyen's message of "Thu, 31 Oct 2013 13:28:44 +0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Pobox-Relay-ID: BC1B61B8-4250-11E3-92CF-1FFB7F2839F8-77302942!b-pb-sasl-quonix.pobox.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 974 Lines: 21 Duy Nguyen 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/