This is usually because of line ending issues. Please see my answer here: https://answers.atlassian.com/questions/185169/sourcetree-win-1-0-3-0-what-happened-to-my-line-endings
To summarise, it's because SourceTree was trying to be helpful with its initial setup to default to unifying line endings - however existing repos may be in a state where this shows up as files needing re-committing to get their line endings into a unified LF format inside the repo (but still CRLF in your working copy).
We've stopped setting this by default for the next update and if you don't want to re-commit these files to change the line endings inside the repo then just remove these lines from mercurial.ini in your home directory:
[encode] **=cleverencode: [decode] **=cleverdecode:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I have the same issue as Neil except I just did a clone from my remote repository and we are not using mercurial. The original repo was TFS. Is there a similar approach to resolve this for TFS to Git? The files in question are *.sql files that have specific CRLF at the top and bottom of files.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.