SmartGit should remember all the open repositories when closing it. I don't see how SourceTree would solve any of the problems you had.

If the target branch is the same as the head branch, you could use Push Up To.

OK, it is different. But why do you think it is better?

To get the SmartGit 20.2 preview, please download it from https://www.syntevo.com/smartgit/preview/ and use Help | Check for Latest Build there.

Could you please show a screenshot of most/all tools that support line-wrap for a file compare? Thanks in advance.

Which file contents should be used in this case? Given such a working

tree state, can you give appropriate Git commands to retrieve these file

contents?

What is the extension of your file? Please give SmartGit 20.2 preview a try: https://www.syntevo.com/smartgit/preview/

Please update to the latest intermediate build 15157 and set the low-level property repositorySearch.autoSearchInDialog to false.

It is much easier to find something in a (alphabetically) sorted list than in a recently-used-sorted list.

But you may change the amount of displayed repositories by tweaking the low-level properties repositories.maxNonFavorite and repositories.maxCount.

There will be no option to switch back to 19.1 style. But what exactly is the problem with the combined node, especially because you can now see the index and working tree files (optionally) in separate tables?