Re: [Monotone-devel] line endings as project policy

[Richard Levitte - VMS Whacker]

So, what I hear you say is that we should remove all the conversion
stuff that exists today.  Is that correct?

Cheers,
Richard

In message <address@hidden> on Sat, 25 Nov 2006 13:52:48 +0100, Ulf Ochsenfahrt 
<address@hidden> said:

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

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         address@hidden
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis