Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Blame in SourceTree for Windows

Achim Hilwers
Achim Hilwers April 15, 2013

Hi!

I have a problem with SourceTree for Windows:

When I use the command "Blame selected", all lines are in the state "Not committed yet" and no changes are shown.

I found out that the standard blame command blames the file in the working copy and as the setting "autocrlf" is "true", all lines are considered to be changed there.

Is there a possibility to change the behaviour of the git blame function to blame the currently selected branch?

Achim

Answer
Watch
Like Be the first to like this
2007 views

1 answer

1 accepted

1 vote
Answer accepted
stevestreeting
stevestreeting
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
April 15, 2013

I've created a feature request for this: https://jira.atlassian.com/browse/SRCTREEWIN-470

If your file is showing as completely modified, and you already have autocrlf=true, then it means it was committed from a machine with an incorrect setting. You will want to normalise the line endings and re-commit it to stop it permanently showing as modified in future.

Reply

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS
AUG Leaders

Atlassian Community Events

    See all events