On Fri, Aug 29, 2008 at 5:28 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > The manual advertises that setting "crlf" attribute to false marks the > file as binary. We should pay attention to this condition in addition > to the "do not diff" attribute (i.e. setting "diff" to false) when > deciding not to show the textual diff. > > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > --- > > * Strictly speaking any change is backward incompatible, and this is > certainly one, but I do not think of a good use case to depend on the > previous behaviour, which was reported as a bug by my coworker. I'm not sure this is a good idea. In our repository, for example, we have a few files that are strictly speaking "text" but absolutely, positively must be CRLF on all platforms because the idiotic proprietary parsers and generators that manipulate them need it to be that way. I think the bug is that "crlf=false" should not be considered the same as "binary=true", which seems to be a bug in the documentation, not the program. Have fun, Avery -- 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
