Hi, On Wed, 20 Dec 2006, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > >> Why SQUASH_MSG? Doesn't it confuse git-explain when it wants to > >> detect that you are in the middle of a squash merge? > > > > Yes, it confuses git-explain. Which did not existed when I concocted the > > first (broken) version of this patch. There are only two ways to give > > commit message templates AFAICT: misusing SQUASH_MSG and misusing > > MERGE_MSG. > > I wonder... > > # An example hook script to check the commit log message. > # Called by git-commit with one argument, the name of the file > # that has the commit message. The hook should exit with non-zero > # status after issuing an appropriate message if it wants to stop the > # commit. The hook is allowed to edit the commit message file. Yes, I missed that. Ciao, Dscho - 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