The new Log window Repo and Branches feature is fantastic.  One thing on the Repos view that I'm missing from the Working Tree window is allow to opening multiple repos

With the new Log window having the Repo and Branches views, and currently limited to "opening" only one repo at a time, is there a need to "Open Repository" on it?

I like how when cloning a repository SmartGit populates the clone url from the clipboard. What would also be nice would be if there was a --clone command line option that would launch the clone dialog using the current directory as the default location in which to create the cloned repository.

This would be especially useful as on Linux SmartGit doesn't seem to have any file manager integration so currently the only way to clone in SmartGit is to open SmartGit, launch the clone dialog, then use the folder explorer to choose where to put the cloned repo. Currently it's quicker and easier to clone using the git cli than to use SmartGit.

The new Perl language syntax is not properly interpreted in SmartGit when showing diffs.

The wrong syntax colouring starts after the defined-or operator (//) introduced in Perl 5.10:

my $review = $model->test // !1;

This is equivalent to C logic:

Review *review = test() ?: nil;

SmartGit interprets it as a comment and colours everything after the '//' with green colour.

Currently, if you double-click on a remote branch in the Log view, you get something like the following:

What I (almost?) always want to do is to checkout the corresponding local branch, but at that commit; in other words, I want to checkout the local branch and then pull. It would be great if there were a "Pull after checkout" checkbox on the dialog, to make this a single action to get where I want. (Bonus points if the checkbox's state was preserved between actions, although I'm not sure of the details of how this would work.)

When our developers starts a new software project, and hence have to configure Git-Flow, they have to manually enter the branch names, which tends to result in differences from one project to the next.

It would be really nice if SmartGit supported loading a conf file with the naming, or even better, allowed the Defaults to be changed, so that when configuring Git-Flow, the names would already be according to the company rules.

I regularly use the "File (expensive)" option and prefer that it was always on.  I would like SG to persist my selected options.

I looked for a "low level pref" for this but did not see one.

If origin branch has diverged (other developer has rebased it in order to do pull request, for example), it might be really expensive to do a simple pull where the whole rebase process is then run locally, even if you had no changes at all, or some minor changes. In ideal world this should not happen, of course.

In those cases, a simple optional warning dialog would be appreciated so that if you do a pull, you can decide whether just to reset the branch and do cherry-picks instead (if needed).

I don't know what would be the reasonable threshold for this, but maybe something like behind 20 and pushable commits 20.

When naming a new branch you can type as normal and hit the space bar in between words. SmartGit will insert an underscore ("_") in place of the space (" ") when making the branch name. I like being able to just hit the space bar and letting SmartGit make the branch name valid, but I prefer to use dash ("-") to separate words in branch names because it is more easily readable to me.

Could there be a SmartGit setting to specify what character should be used to replace spaces in branch names? This could let people use "_", "-", "+", or even "/" as they prefer.