Stash: where is the “Include untracked files” checkbox?
It has been moved into the preferences, “Commands” page.
Push To: where is the “Force pushing” checkbox?
It only was there because of a bug. For forced-push, you will need to select the “Allow modifying pushed commits” checkbox in the preferences, “Commands” page.
We want to better understand the needs of our SmartGit users. What are the key benefits of SmartGit and at which areas does SmartGit lack features or needs polishing.
Please request new features at smartgit.userecho.com or share your pros and cons at slant.co (for Linux, Mac or Windows).
Thanks for your time and help!
One of our Windows users recently ran into a strange error when trying to clone a GitHub repository, telling him “protocol https not
supported or disabled in libcurl…”. As it has turned out, he is using PureData which seems to cause troubles in combination with Git, according to this stackoverflow posting.
Switching from his custom Git to SmartGit’s bundled Git has solved the problem for him.
Usually, an SSL handshake_failure is caused by providing a bad client certificate.
If this is not the case, you may add following line to smartgit.properties:
and launch SmartGit from the console (on Windows, use smartgithgc.exe).
The resulting debug output may give hints on possible other reasons. Sometimes it may still be meaningless as it was the case for a support request we have received today.
The relevant part immediately before the error just showed up:
QThreadPoolThread-12 (smartgit.SZ), READ: SSLv3 Alert, length = 2
QThreadPoolThread-12 (smartgit.SZ), RECV TLSv1 ALERT: warning, handshake_failure
SSL - handshake alert: handshake_failure
QThreadPoolThread-12 (smartgit.SZ), handling exception: javax.net.ssl.SSLProtocolException: handshake alert: handshake_failure
QThreadPoolThread-12 (smartgit.SZ), SEND TLSv1 ALERT: fatal, description = unexpected_message
As it turned out, the SSLv2Hello protocol needs to be enabled by adding following line to smartgit.properties:
After restarting SmartGit, the problem should be gone.
Version 5.0.9 contains updated SSL fingerprints for GitHub and BitBucket.
Since Bitbucket certificates have changed, SmartGit refuses to connect (“SHA fingerprint of certificate does not match”). We will update fingerprints for version 5.0.8. In the meanwhile you may use the latest build (Help|Check for Latest Build) or your may fix it manually by adding following line to
smartgit.properties (in the SmartGit settings directory, see About dialog):
After restarting SmartGit, connection will work again.
Edit: As of February 25th, 2015, the official fingerprint as it shows up in the web browswer is
For SmartGit/Hg, our graphical Git client with SVN and Hg support, public preview builds for the upcoming version 6 are available. The most important changes are (detailed change log):
- Completely reworked repository management
- Background fetch and refresh
- Distributed Code Review similar to the existing GitHub integration, but without the need of GitHub
- Markdown support for GitHub integration and Distributed Code Review
You are welcome to give it a try!
Download the preview build