@Marc: Thanks for this detailed explanation about the downsides and problems including SSH support.

However after reading this, I started wondering if there was not maybe a different way to achieve the same. What if SmartGit included a possibility to mount a server path with SSHFS and could then work with those files as if they were on the local disk?
Of course users can mount SSHFS manually, but when dabbling with that in the past on my Mac I found the available solutions quite lacking … I'm not sure if anything changed in the past 5 years. So wouldn't it be interesting for SmartGit to invest time on that end to get a solution built into the client directly?

I just found this thread while trying to find out if SmartGit supports working through SSH. I always had my repository directly on the development server, then needed to change my way of working when starting to use SmartGit. Now I have my repository locally and push all changes to the web server to test it.

This works but it's more cumbersome, all the more with working 3 days per week in home office and 2 days on site. Support of controlling a repository through SSH would be a huge advantage.

Of course as a developer I understand the reluctance of starting a complete rewrite, but on the other hand, in a competitive market it's all about going the extra mile …