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 checked that -w covers
eol whitespace, but I am expecting that it does;-)
For the actual EOL change, you don't say if it's an open source (many / few
contributors) or closed/corporate code (again, how many).
for closed source - few contributors it is faily easy to declare a change
over day and 'make it happen' - just freeze the master repo, do a one shot
change on all major branches, and make everyone pull the change, and update
their personal branches.
If its Open/few, or Closed/many, then a little more planning and persuasion
is needed, but it's very similar.
for open/many you will need a persuasive strong maintainer with a dictator
(benevolent) streak, and time to let it bed in, to ensure that everyone
"get's the memo". It's guite likely that different 'religions' will form
schisms as the code base fractures if all those people issues aren't handled
carefully.
Mostly its a social issue, with a little bit of clarity for tagging the last
old style versions, single commit fix of eol ONLY, and tag that, and move
on.
If you have eol, tab-spacing and spaced-out endings, then you should have
three separate commits, one for each tight issue. It saves a lot of
'discussions' later!
If you do have trailing white space requirements (i.e. code that must have
it) then think hard about how that is to be managed and indicated, because
it cannot be seen, and is a recipe for disaster.
--
Philip
PS never had to do it myself. Do read other folks methods, ask why they
suceeded/failed, and then decide what is best for you.
----- Original Message -----
From: "Michael" <keybou...@gmail.com>
To: <git-users@googlegroups.com>
Sent: Friday, December 23, 2016 5:38 PM
Subject: [git-users] Best approach to convert a CRLF repository to LF?
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 file as changed, and "git
blame" listed the person doing the conversion as responsible for
everything in the repository, with all lines at that date and time.)
--
You received this message because you are subscribed to the Google Groups
"Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
