In the Log Graph, if a particular commit (A) has been reverted in a future commit (B), add some indicator on commit A to highlight this status.

Ways to highlight include italicizing the text, graying out (graying out is being used for merge-commits), strike-through, different color, different font, smaller font size, etc.  (I vote for strike-through).

Benefits: When reading a graph from bottom to top, it would be helpful to tell the user that this particular commit has been reverted.  This allows the user to get even more meaningful data from the log. 
I find it particularly useful when writing Release Notes, or to avoid making quick assumptions that a particular feature has been implemented just because a commit for it exists.

Potential implementation:  It may be taxing to the CPU to scan the entire repository, so we could limit it to just visible commits (branches/refs that are checked).

See initial brainstorming page on Google Groups:  https://groups.google.com/forum/#!topic/smartgit/_ARrXyUQzFU

I often find myself copying the current draft commit message (in case something goes wrong), close the commit window, open the log for one of the files I'm about to commit and then re-open the commit window.

It would be nice to be able to open the log window for one of the files I'm about to commit from the commit window directly.

Since v18.1 : "The default log coloring now uses adedicated color for each selected refs (unless there are too much)"

This is stunning when having 4-5 branches checked, it really helps the log readability !
But I saw also that if I check the tags then they are counted as selected refs, and the log switch to 2 colors (white for current branch and purple for other branches).

May this count be done only on branches and not tags ?

SmartGit currently creates a `.smartgit/` folder in the user's home directory on Linux. Most programs don't create a folder in the user's Home directory anymore and instead use the Freedesktop `$XDG` standard found here: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html.

Using this standard:

• `$XDG_CONFIG_HOME` – says "configuration files" go to `$HOME/.config/`
• `$XDG_DATA_HOME` – says "data files" go to `$HOME/.local/share/`
• `$XDG_CACHE_HOME` – says "temporal/non-essential files" go to `$HOME/.cache/`

This is just a request to consider using this standard. It makes a lot of sense; it is easy for the user to understand, makes it easier to backup/locate/restore/manage/clear user's data, and creates less clutter in the user's home directory.

Thanks in advance...and thanks so much for everyone's hard work on this program – it's amazing!

Selecting "View > Only Index" or "View > Only Working Tree" adds a segmented control in the interface, but when you select "View > Mixed" (or not select the first two options at all), no control is present in the interface.

It would be awesome if all 3 of them would be in the interface like "Mixed | Index | Working Tree" so you can easily switch between them any time.

Now I can see file diff when chose two commits in log interface

I'd request a feature that shows analytics info about the diff between the commits

For now I think add a right menu item "show diff analytics" and popup a new window would be fine

Infos can be shown:

- count of added files
- count of deleted files
- count of modified files

- count of added lines
- count of deleted lines
- count of modified lines

- every person's contribute between two commits(commit count, modified file count, line count)

Request by a user:

If in some projects users merge, get conflicts, solve and commit & push without further tests, it might help a little bit if the "Commit & Push" button would not be enabled while trying to commit in the merging/rebasing state. This option should be project based and triggered by a file that can be committed to the repository.

Please add support for the latest Mercurial version! My org mandates using our own modified Mercurial clone branched off of 4.7, so I can't go to 4.5, which SmartGit 18.1 supports :(

Newer versions of git support Watchman (https://github.com/facebook/watchman), which vastly improves the speed of local Git background operations. Would be awesome if SmartGit dealt with setting it up for repos.

Git support announcement: https://blog.github.com/2018-04-05-git-217-released/