On Fri, 2010-10-22 at 11:18 -0500, Jonathan Nieder wrote: > Hi, > > Drew Northup wrote: > > > This is part of my ongoing work to treat UTF-16 as text (in > > other words, the crlf options will work and .gitattributes hacks won't > > be required to display diffs, etc). > > What's wrong with .gitattributes for this use case? I would think a > clean/smudge filter would produce very good behavior from most git > commands. > > If speed is the issue, maybe a built-in clean/smudge filter would > address that? That still doesn't fix the crlf issue, for starters. Also, I would like to be able to email patches for files that are in UTF-16 and properly re-import them. Unless I'm missing something really big there's not much that a display filter is going to do for me there. I want this to be two-way. To be honest, the not needing of a display filter goes along with treating UTF-16 patches as text. The same sort of code will be required for both, so why not get predictable behavior for another text encoding at the same time? -- -Drew Northup N1XIM AKA RvnPhnx on OPN ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- 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