In my work flow, I am using a pre-commit script that (among other
things) rewrites all text files to have \n endings. This is a one-way
conversion, and does work well for the set of tools I am using. The
converters I use I wrote years ago, and are smart enough to deal with
mixtures of \n, \r\n, and \r line endings in one file, transforming all
into one unified form. d2u / u2d were not that robust when I last tried
them (years ago), but this is an absolute necessity.
However, I don't think the one-way conversion is acceptable across the
board. While the only Windows editor I am aware of that doesn't grok \n
is Notepad (the moral equivalent of edlin), I suspect that undo reliance
upon this will still lead to grief. If nothing else, someone, somewhere
will find that their beloved crlf's are missing and will complain.
Loudly. And in the lore, git will become known for being "wierd." So, I
suspect a checkout script is necessary.
Mark
-
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.html