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.

The changes view has a great diff part. This diff shows the changes between the previous and the current revision. However I sometimes have trouble telling both apart. This might arise from using Eclipse, as in its diff view the order is different. (Don't pin me down on that,  it can switch sides to add  to the confusion).

What would really help me is some additional information in the diff part. Annotate the header with a commit date and/or the author. Or just adapt the tab title to: Changes of File (Modified, old-sha vs sha current).

I have many repo groups, some with only a few repos and some with over 20.  I use the "fetch in background" feature to do so when online, in case I am soon working offline, and also as a local preview of incoming changes.

With many repos having fetched changes, similar to Pull/Push on selected repos and repo groups, I want a single menu option to rebase each repo to the fetched changes.  This would save a lot of manual processing work and waiting time on many updated repos, especially repo groups with larger repo quantities.

In SnapshotCM, this program will always make a .bak copy of the file (saved in the same folder) on every "Discard" message.  If there is already a .bak file, it just increments to .bak1 on the next "Discard".

This feature is really handy to cater the case of accidental Discards (e.g. laggy computer, clicked on wrong button).

Having a bunch of .bak file in the workspace was a bit annoying.  So, if SmartGit wants to implement a similar safety feature, I suggest:

• Saving it somewhere in %localappdata%.  It can probably just follow the hierarchy of the workspace.
• User then invokes a "See backups" button, which opens up a window (like the Log Window).
• By default, save only up to 5 backups per file (or something like that, to prevent extreme accumulation).  The idea is to mainly to cater accidental Discards, or recent Discards.
• It can be turned off by default, and is an opt-in option so user knows where the backups are saved (or perhaps allow the user to pick a backup space).