This line ending thing is getting far too much attention, IMHO. My last
word on this issue is:
- Whatever I check in, I want checked out
- What I'd like to see is a setting where monotone checks on commit if
the files obey a particular line ending convention/charset and gives a
warning if they don't
I don't want any automatic conversion of line endings or charsets. IMHO,
charsets are much too fragile and dangerous to be handled by monotone.
And line ending conversion cannot really be separated from charset
handling in the face of non-8-bit encoded charsets.
That said, I am not opposed to an opt-in mechanism for line
ending/charset handling, as long as its not on by default.
The CVS way to do it was really, really bad. It messed up my files
several times, with duplicate line endings and with treating binary
files as text.
Now, there's also another thing, which is a better merge ui, which is
much overdue now...
Monotone-devel mailing list