Adrien Beau wrote: > On 2/27/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> 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.) > I think the question is whether completely empty lines are also ignored by Python, or if they start a new block of code. Whatever the case, it must hold true for both 2.3 and 2.4. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Mon Feb 27 22:42:41 2006
This archive was generated by hypermail 2.1.8 : 2006-02-27 22:42:53 EST