Creating a new group is buried under the 'Move to...' context menu. Drag & Drop users have trouble discovering how to create a group.

Allow to select multiple repositories and Push, same as you can do with Pull. Handy when you've got a lot of changes in multiple repositories to synchronize.

I don't care how it's done: hovering over the commit row to see a multi-line tooltip, or selecting the row to vertically expand the row, or whatever... but it's important to be able to read a full commit message in the journal window. I hate having to bring up the log, then locate the same commit row and select it just to read whatever caught my interest in the journal window. I almost cringe at reading the journal window now, as a result. I might as well just turn it off.

Suggestion:

Currently, there are two separate 'Output' windows: in main window and 'Log'. I suggest to synchronize them, that is, make sure they have identical content at all times.

Rationale:

Depending on where you run a command from, its output ends up in one of those. I routinely run 'Rebase HEAD to...' from Log, then 'Continue rebase' from main window. Parts of the output ends up in 'Log', and another part in main window. To make matters worse, closing and reopening Log window during rebase will wipe its portion of 'Output'.

The same column recently added to the Files window in the main view.

Please, add https support to the lic-update page.

I find that sometimes if I close a view in the SmartGit workspace I forget how to get it back. Also, I imagine that different users have different tastes in what consitutes and efficient SmartGit workspace. It would be nice if the current layouts and dimensions of views could be saved as a named workspace that could be called up later.

Essentially, the Main and Review "Perspectives" are pre-defined workspaces. All I am suggesting is to allow users to name and use other arrangements of workspace views.

I often want to archive to zip format a set of commits. I use this: git archive --output=file.zip HEAD $(git diff --name-only HEAD^ 6b1fee558318cc9cd65b3369c5a33de4a131694f )

This is great except when the resultset from git diff has too many entries. This may be because we have commit A, B, and C. Commit A modified 10 files. Commit B added 4,000 files and Commit C modified 5 files. Ideally I would like to be able to select only Commit A and C from the log and pass them to git archive instead of passing a range of commits. This allows me to avoid Commit B with the many added files.

Also, it would nice to have this functionality within a GUI

That's what I intuitively expect when right-clicking on the empty space in "Branches" view -- the popup menu with "Add remote..." item (well, if some element of the "Branches" list is already selected, right-licking anywhere shows its contextual menu, which makes some sense; but the problem is that left-clicking on the empty space doesn't deselect, which is counter-intuitive).

Adding "Stash..." menu item also makes sense

I have a big file which couldn't get diffed in the main window. So I increased the size limit in the preferences file, but now, every time I select it, the diff process starts automatically and hands the background thread of the app (the UI is not blocked though). Even if I just want to commit it.

For binary files, there is a button named "Force Text", which works similar to my idea, which sounds like this:

The user changed the diff limit size:

- Y:

- the user selects a file whose size is bigger than the default one:

- Y: a "Force Diff" button appears

- the user presses the button: the diff process starts

- N: the diff process starts

- N:

- the user selects a file whose size is bigger than the default one:

- Y: the "File is too large to display." message appears (optionally, with a button that (creates? and) opens the preference file, or better yet, move those configurations in the UI)

- N: the diff process starts

Let me know if I was clear enough!

Thank you,

Iulian Onofrei