Your comments
Absolutly not :) I found this : https://www.syntevo.com/doc/display/SG/Local+Operations+on+the+Working+Tree
I'll need to try on next amend and rebase...
For a commit, the git revert command is fine and works great in SmartGit.
But I found myself quite unhappy when rebasing a branch or amending a commit indeed, and then an "undo" option would have been great !
Hi,
The mix of gray and black weren't present in the first versions and believe me, they are mandatory ;)
For the toolbar background color I was also happier with a dark background : the last version before switching back to light gray was better looking, and also easily readable... in my opinion :)
Oh ok, thanks !
Installed the latest build (#9064), and the dark theme is not working anymore ? My smartgit.properties still has smartgit.theme.file=dark but it seems this has no effect anymore, I've got the default Smartgit interface...
Indeed the default configuration for journal view works really well when using the GitFlow model (feature / hotfix branch especially)
Just restored defaults colors on the latest build (#9047), and I see light colors in the ruler and nice colors in the editors. It's very nice now, bravo !
Ok... Was the case on the first release, but it was really ok for me on the latest one (previous 9061)...
What do you mean by managing issues ?
Are you aware of the Git Bugtraq integration in SmartGit ?
Customer support service by UserEcho
Thanks for your comment, but I don't agree this need should be filled up by a GIT client : what you're trying to see is the differences between the index and your working tree. This is more the job of your IDE or editor, and is indeed implemented in many of them (Eclipse - with its quick diff feature - , Netbeans, WebStorm, ...)
History of a specific file, and blame on one file are already very well handled in so much editorsI don't see the point of exiting your editor, switching to the GIT client and call the corresponding functionnality... when one shortcut can directly give you the information you need.
A graphical GIT client should be "GIT centric", so "log centric" : you want to see list of branches and their different origins, what where the previous changes and what changes they contains, a good view of both the working tree and the staging area, ...