Make sure you download the 1.6.1 version as that is really the latest:
SourceTree 1.6
Enhancements
All new file status view
Improved diff view
New view configurations
Cleaner user interface
All new welcome wizard
SourceTree 1.6.1
Bugfixes
SRCTREEWIN-1902: Fix crash bug when trying to create a new repo from hosted repos screen
SRCTREEWIN-1915: Fix a rare crash bug which could happen when closing/re-opening a repository
SRCTREEWIN-1894: Staging/unstaging will get ‘stuck’ and not refresh the file list if you turn on ‘always display full console output’ when performing these operations. The refreshing now happens regardless of whether that option is turned on or not.
SRCTREEWIN-1897: Fix a crash bug when listing Stash repos from hosted repos list.
Confirming removing files now shows the file names in a list so you know which files you’re removing
SRCTREEWIN-1909: Can now commit files if committing individually even if they’re at the root and not using staging (so either Mercurial, or no staging mode in Git)
I had my userid jeroenp show on all my commits, issues and other activity on BitBucket, though in SourceTree, hg config, gitconfig, etc I had configured my full name.
hg flow -y -f init
abort: No module named ConfigParser!
Full error message (the middle line is funny “flow: Flow was already initialized for workspace:”):
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
There are a few more messages in the “Missed Schedule” backlog, and I really hope that WordPress is going to address this really annoying bug soon as I have to recheck my blog multiple times a day now.
Back on topic:
Development tools should become more version control friendly, and version control tools more whitespace tolerant
I’m taking Delphi and Bitbucket here as an example, but this holds for many more development tools and version control tools.
Ultimately, you want changes to be as simple as this one: only the relevant changed lines show up as an actual change.
But often changes include convoluted non-relevant information.