SmartGit SVN integration: end-of-life announcement

SmartGit’s SVN integration will be discontinued on Dec 31, 2022. We have decided to take this step because the amount of users of the SVN integration is steadily decreasing and is already less than 1% of overall Git users. On the other hand, the SVN integration affects many code parts, making them harder to maintain/change. Also, the support effort for non-default SVN server layouts is quite high. When putting increased maintenance effort into relation to the low number of users, we believe that dropping the SVN integration will be beneficial for our overall user base.

What does that mean for you?

If you are not accessing SVN repositories, this will not affect you at all. Note that former SVN repositories which have been converted to Git once and since then are only used as Git repositories (i.e. no more pulling/pushing back to SVN) are actually pure Git repositories and thus will not be affected.

If you are actually still accessing SVN repositories, you can continue using the latest major version released before Dec 31, 2022 even after this date (of course, only on the operating systems supported by these versions) to clone/push/pull to your SVN repositories. There will be no more bug-fixes to the SVN integration for these versions after Dec 31, 2022, though.

For major versions released after Dec 31, 2022 the pure Git functionality will continue working with already cloned SVN repositories, but pulling/pushing (or cloning new repositories) to/from SVN servers will not be possible anymore.

We recommend to convert your SVN repositories to Git or use SmartSVN to access them.

SmartGit 21.1 preview 1

The first public preview build for SmartGitĀ 21.1 is available.

The most important improvement are

  • rewritten Changes view with Unified view, syntax coloring even in compact mode, manual expansion of hidden lines in compact mode, apply changes in compact or unified mode, too
  • Cherry-Pick on a file selection
  • Split-Off Commit on a file selection
  • Interactive Rebase to stop at every commit, step by step or continue,
  • performance improvements

Download
Change log

Linux with GTK <3.20

SmartGit 20.2.1 will allow to switch to an alternative SWT implementation which supports GTK <3.20. If you are running such a system, SmartGit will tell you on startup. Following steps will be necessary:

      1. If you have installed SmartGit < 20.2.1, install the latest bundle from the SmartGit download page.
      2. Locate smartgit.vmoptions: usually it’s located at ~/.config/smartgit/smartgit.vmoptions (if not present there, check the parent of SmartGit’s settings directory, as displayed in the About dialog). Add following line to this file:
        swtver=4932
      3. Restart SmartGit: if everything is configured correctly, SmartGit will print an information about a custom SWT version to terminal and should start up properly.

Linux: why we recommend the tar.gz bundle?

For Linux we are offering since ever a .tar.gz bundle and since a couple of years a .deb bundle.

We recommend the .tar.gz bundle, because

  • it can be installed simply by unpacking anywhere,
  • it can autoupdate itself to any newer version, even if the installation directory needs to be updated,
  • it ships will all dependencies (except of libcurl), including Git and JRE,
  • workarounds like for outdated GTK3 versions are easier to handle

SmartGit on macOS 11 (BigSur)

SmartGit 20.2 is the only version which we officially support on macOS 11. There are some known UI-related problems which we are working on.

SmartGit 20.1 is not officially supported on macOS 11. Still, according to user’s feedback and our own experience, SmartGit 20.1 is basically working on macOS 11, however there are a couple of known UI-related problems: some of them are resulting in crashes, others only resulting in UI-glitches. The most pressing of them are already resolved in version 20.2. If you are running into any unexpected problems, please upgrade.

SmartGit 19.1 and earlier are not supported on macOS 11. These versions are known to have several problems on macOS 11. We definitely recommend to upgrade to version 20.2.