Tags

Postings

  • SmartGit 7 rc 1

    The first release candidate for the upcoming SmartGit 7 is available.

  • SmartGit 7 preview 14

    A new preview build for the upcoming SmartGit 7 is available.

  • Windows 10 table control: area right beside column header is black

    SmartGit, SmartSVN and SmartSynchronize show a black area right beside the last column in the header area.

  • SmartGit 7 preview 13

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartGit 7 preview 12

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartGit, SmartSVN, SmartSynchronize hang on OS X 10.11 beta 3

    SmartGit, SmartSVN, SmartSynchronize and a lot of other Java-based (GUI) applications, e.g. Eclipse, hang on OS X 10.11 beta 3 / public beta 1 (El Capitan). They worked on previous OS X 10.11 beta versions.

  • SmartGit 7 preview 11

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartSVN OpenAPI deprecated

    For upcoming SmartSVN version 9, we are going to deprecate the OpenAPI. For the next major version (after release 9), the OpenAPI may be removed entirely. The functionality of all bundled plugins (e.g. the JIRA plugin) will be preserved.

  • SmartGit 7 preview 10

    A new preview build for the upcoming SmartGit 7 is available. It adds rudimentary Hg bookmark support and fixes a couple of bugs.

  • SmartGit 6.5.9

    This release fixes a few bugs. We recommend to update.

  • Why we ask non-commercial users to run a recent SmartGit version

    Non-commercial users sometimes complain about warnings and final deactivation of older SmartGit versions. Now why are we doing this?

  • SmartGit fails to start on Windows

    If you try to launch SmartGit and see a “Couldn’t load main class.” error, be sure to check the TEMP and TMP environment variables. They should point to a directory where the current user has write access (references).

  • SmartGit 7 preview 9

    A new preview build for the upcoming SmartGit 7 is available. The most important change is the use of the hg executable for all operations (independent of Hg4J now).

  • Crash on KDE

    If SmartGit, SmartSVN or SmartSynchronize crashes for you on dialogs where (on other platforms) comboboxes are visible, please check whether the oxygen-gtk style is selected. It is reported to be extremely buggy and better should be replaced with either Adwaita or Clearlooks-Phenix:

  • SmartGit 7 preview 8

    A new preview build for the upcoming SmartGit 7 is available. It fixes 2 nasty regressions from 7 preview 7.

  • SmartGit 7 preview 7

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartGit 6.5.8

    This release fixes a couple of submodule and GitHub related bugs. We recommend to update.

  • SmartGit 7 preview 6

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartGit 7 preview 5

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartGit 6.5.7

    This release fixes a couple of bugs and adds support for GitHub’s latest authentication changes. We recommend to update.

  • SmartGit 7 preview 4

    A new preview build for the upcoming SmartGit 7 is available.

  • Hard crash when viewing certain files on Linux

    A few users have reported that SmartGit might crash when viewing certain files in the Changes preview of the repository or log window, or Compare. Until now this has to been reported only for Linux. Fortunately, a friendly user provided the details to make it reproducible for us.

  • SmartGit 7 preview 3

    A new preview build for the upcoming SmartGit 7 is available.

  • SmartSVN: missing/unversioned file pairs on OS X

    We are frequently getting bug reports of “normal” files showing up as a missing/unversioned file pairs on OS X. This happens if they contain non-ASCII characters (like German Umlauts) in their names and they have been added from another platform, like Windows or Linux or directly from the Repository Browser.

  • Invoking SmartGit's blame from Visual Studio

    One of our users has just shared a solution with us to invoke SmartGit’s Blame directly from within Visual Studio: in **Tools External Tools**, SmartGit has to be configured as new tool with appropriate command line parameters: