Johannes Schindelin wrote:
Hi,
On Mon, 12 Feb 2007, Mark Levedahl wrote:
Perhaps I'm too paranoid, but I've been burnt way too many times by
text/binary mode stuff to let this part be trivialized. Maybe it only
gets enabled by core.ImReallyParanoid, but I want that option.
Be aware that what you proposed costs many CPU cycles. I am totally
opposed to enabling that option by default on all platforms. I am okay
with .gitattributes (but I would call it .gitfiletypes), but I am _not_
okay with git being _too much_ fscked up by Windows. Microsoft has done
enough harm already.
I would assume that none of this crlf stuff exists at all on Linux /
Unix / Posix, so if done right has zero impact outside of the Windows
nuthouse. Inside that, folks are already so used to incredible slowness
in file I/O that I'm not sure the round tripping I suggest as a check
would be very noticeable, but in any case I fully agree it should be
optional even there. However, if git could support something that never
screws up, absolutely guaranteeing data integrity in the presence of
these transforms, that would be a first in this arena and I believe a
significant selling point.
Mark
-
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