As far as I know (I ran into this with BladeQuest) is it has to do with the editmode of the file.  I think the \r only shows up when opening files made from specific platforms in binary mode, but otherwise it is supposed to update them \r's out for you.

You might be safe just ignoring them completely but there's a question of if there are any platforms that only use \r...it's kind of an annoying possibly-nonexistent problem.

If you really wanted to cover all your bases you could find+replace '\r\n' as '\n\' and then after than find+replace '\r' with '\n' which shouldnt double-count because as far as i know \r only ever precedes \n.

In the end we should probably just take the line info from the git blame and compare it to the comment we captured which will verify if we got the line number right and then throw out that todo if they don't which would mean that their line ends format is fucked.