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

Add a panel that will be exposing the OS CLI opened in the project's folder.

I use SmartGit for both Git and Mercurial, which is great: I have just one tool learn, and the same tool on Windows and on Mac. But, the commands and preferences for the two VCS are inconsistently implemented. For example:

The preference "Stash: Automatically save stash if Pull, Checkout, or Interactive Rebase fails because of local changes" works for Git but not Mercurial. Similarly, the Apply patch menu item uses the git apply command rather than the Mercurial import command even when pointing to a Mercurial repository.

SmartGit should be smart enough to know what sort of repository it is executing against and use the appropriate command, or tell us when that command hasn't been implemented.

Also, perhaps there needs to be separate preference tabs for Git- and Mercurial-specific preferences as there are some siginificant differences.

SmartGit allows you to create and apply a patches for Git, but not for Mercurial. Atlassian's SourceTree and the tool within Intellij IDEA have a context menu against log entries to create a patch from single or multiple commits.

Tools configured in the Preferences should work on the Log's File view in a similar way as in the main window