Hi Norman,

>> A number of source files in my (Windows) CVS working dir have Unix line 
>> endings though, whereas their Git counterparts have DOS endings.
>>
>> That's no problem, as long as it doesn't lead to a huge number of 'changes' 
>> and log messages when such a file is committed, cluttering the history and 
>> drowning the real changes.
>
> This is a documented feature of Git.
>
> Github has a document about how you can set up your git client to cope 
> with this. The URL is 
> https://help.github.com/articles/dealing-with-line-endings/.

(...)

> So, windows users need:
>
> $ git config --global core.autocrlf true
>
> and Linux and Mac users need:
>
> $ git config --global core.autocrlf input
>
>> Anyway, I guess that won't occur if we commit all our work to CVS before the 
>> conversion/transition, get a fresh git clone afterwards and work only from 
>> that. Am I right?
>
> In a word, yes. Provided that you configure the Git client before 
> checking out and definitely before checking in.

It's a bit risky to have it depend on the client, i.e. the individual user. But 
I see now that you can also take care of it in the .gitattributes file, and 
Mark has alreay done that.


Cheers,
Paul

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs

Reply via email to