Tags
Postings
-
SmartSynchronize 3.3.6
Among other, less important changes, version 3.3.6 fixes a serious problem regarding UTF-encoded text files. Please update if you are using 3.3.5.
-
SmartGit/Hg 6.0.7
This release fixes a couple of bugs. We recommend everybody to update.
-
SmartGit 6 on OS X 10.6.8
Officially, SmartGit 6 requires OS X 10.7 or higher, but, depending on your system, it may be possible to get it starting on OS X 10.6.8, too: right-click SmartGit.app, click “Show Package Content”, navigate into “Contents/MacOS” and open “SmartGit” in a text editor of your choice. There you’ll find the line
-
SmartGit 6.5 preview started
The first public preview build for the upcoming SmartGit version 6.5 is available. The most important changes are:
-
SmartGit/Hg: sparse checkout
From time to time we are asked whether SmartGit supports sparse checkout? The answer is: it does once configured. Let’s assume you have a remote repository with two top-level directories:
-
SmartGit/Hg 6.0.6
This release mostly fixes a couple of bugs, most notable for the Distributed Review add-on.
-
Launching Terminal (cmd.exe) from Java
Until now SmartGit used following command for its default Open in Terminal external tool:
-
SmartGit/Hg 6.0.5
This release mostly fixes a couple of bugs.
-
SmartGit/Hg 6.0.4
This release mostly fixes a couple of bugs.
-
SmartGit/Hg 6.0.3
This release mostly fixes a couple of bugs.
-
SmartGit/Hg 6.0.2
This release mostly fixes a couple of bugs.
-
SmartGit/Hg 6 released!
We are proud to announce the official release of SmartGit/Hg 6. The most important new features are Distributed Review, Background Fetch and Reworked Repository Management. Check out What’s New for a more detailed list of improvements in version 6.
-
SmartGit/Hg 5.0.10
Version 5.0.10 contains a couple of bug-fixes.
-
SmartSynchronize 3.3.4
Version 3.3.4 adds a few smaller new features and fixes a couple of bugs. Because it requires Java 7, it must be downloaded and installed freshly.
-
SmartGit: "protocol https not supported or disabled in libcurl..." error
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.
-
SVN: SSL handshake_failure
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:
-
SmartGit/Hg 5.0.9
Version 5.0.9 contains updated SSL fingerprints for GitHub and BitBucket.
-
SmartGit/Hg 5.0.8
-
Bitbucket Certificate Problem
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): -
SmartGit/Hg 6 preview
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):
-
SmartGit/Hg 5.0.7
-
SmartGit/Hg 5.0.6
-
SmartGit/Hg 5.0.3
-
SmartGit/Hg 5.0.2
-
SmartGit/Hg 5 released!
We are proud to announce the official release of SmartGit/Hg 5. The most important new features are GitHub pull requests and comments and Issue linking. Check out What’s New for a more detailed list of improvements in version 5.