On 2/27/06, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > there is a good reason not to enable the no-whitespace-at-eol checking in > pre-commit by default (at least for *all* files) for git development: > > Python. > > Just do a "/ $" in git-merge-recursive.py. These whitespaces are not an > error, but a syntactic *requirement*. No, they aren't. A logical line that contains only spaces and tabs is ignored by Python. (All the "dirty" lines in git-merge-recursive.py are such lines.) Besides, spaces, tabs and newlines can be used interchangeably to separate tokens, so trailing whitespace is never *required*. Hope this helps, Adrien - : 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