The interactive rebase is exactly made for the purpose of performing a couple of operations at once. Contrary to what you write, when squashing a commit there, you will already see the future single squashed commit. What exact information are you still missing here? Please note that we won't add a "log graph" to this dialog because commits will be only linear anyway.

You can do that by using View|Set Anchor Commit (only enabled for Merge and Branch coloring)

Did you already try View|Branch Coloring?

I've removed the "Allow more than 1 level grouping" part of this RFE. If multi-level branch hierarchy is important for you, please vote for: http://smartgit.userecho.com/topics/544

Have you enabled Git-Flow (Light) and configured "master" as your develop-branch?

I have just uploaded 17.1 preview build 11069 which comes with two improvements:

- in certain situations, parent colors are better preserved (requires Git-Flow to be enabled, so SmartGit will know that "develop" is more important than e.g. "features/foo")

- with system property smartgit.log.graph.layoutActions=true set, the graph context menu provides a new option to Toggle Preserve Parent Order (for which effects may be more frequent/visible if Git-Flow is disabled)

I still agree with Jonathan: when following first parents commits of master down the Log, the color should be preserved as long as possible. For the specific example, red color is preserved for the merge source instead of the primary parent. That should be changed.

Thanks, I can access the test repository, however the graph looks fine for me. Do you have system property "smartgit.log.graph.layoutActions" set and do you have modified the Max. Connector Length? If so, please send your settings.xml directly to smartgit@syntevo.com

Is this repository public, so I can reproduce the problem?

It should work for Git-SVN repositories now, starting with version 17.1 preview, build 11065. Would you please give it a try and confirm?