Re: Importing Mozilla CVS into git

[Jakub Narebski <jnareb@gmail.com>]

On Sun, 4 Jun 2006, Linus Torvalds wrote:

> On Sun, 4 Jun 2006, Robin Rosenberg (list subscriber) wrote:
>> 
>> (Yet) Another problem is that many windows tools use CR LF as the line ending.
>> Almost all windows editors default to CRLF and some detect existing line 
>> endings. No editing with notepad anymore. Of course that is a problem 
>> regardless of whether a git or cvs client is used. You'll get these big 
>> everything-changed commits that alter between CRLF and LF.
> 
> The only sane approach there (if you want to be at all cross-platform) is 
> to just force everybody to _commit_ in UNIX '\n'-only format. Especially 
> as most Windows tools probably handle that fine on reading (just have 
> trouble writing them).
> 
> And that shouldn't actually be that hard to do. The most trivial approach 
> is to have just a pre-trigger on commits, but let's face it, that would 
> not be a good "full" solution. A better one is to just make the whole
> "git update-index" thing just have a "automatically ignore CR/LF" mode.

Why wouldn't it be good solution?

BTW. wouldn't Mercurial encode/decode filters

  http://www.selenic.com/mercurial/wiki/index.cgi/EncodeDecodeFilter

be a better solution than modifying files by "git update-index", 
with all problems it can cause (not detected binary files, text files
which have to be in CR/LF line ending,...).

-- 
Jakub Narebski
Warsaw, Poland