Hi Igor,
In line with almost all "version control" systems, Git takes the view that what
is in the reposititory 'is' the versioned artefact, rather than some small
(allowable?) variant of it.
There is some on going work on ensuring that the CRLF line ending choices of a
user can be
What is the best way to convert a CRLF repository to LF? Assume that everything
in it is a text file, it had been developed on a windows system and is now
going to support windows and unix, and we'll be switching to automatic linefeed
translation.
(The last time we tried this, it listed every
Michael,
last things first; I guess you did some googling after you sent the question
(I find I do that) http://www.lmgtfy.com/?git+blame+ignore+eol give a few
clues.
The main one is that 'git blame -w' will ignore whitespace changes. Also
'-M' will ignore moves as well! Haven't personally
Hi Philip,
Thanks for the extensive answer. I`ll address my concerns inline, please
excuse me if my lack of *nix background gets too obvious, I might be
missing some well known facts.
In line with almost all "version control" systems, Git takes the view that
> what is in the reposititory 'is'
