From time to time SmartGit users contact us because their SmartGit has expired and they want to continue to use it free of charge for non-commercial purposes.
The type of usage you have to select on the first SmartGit start.
If you forgot to set the right option and you started an evaluation for commercial purposes,
- exit SmartGit
- clear SmartGit’s settings directory (see the documentation)
- restart SmartGit and select the non-commercial option
A couple of users reported strange bugs of SmartGit.
Their sent log files revealed that some other application seemed to have cleared SmartGit’s temp directory while it was running.
We’ve got following mail from Jon Phipps who seem to have found a possible reason.
We thank him for letting us know and want to share his experience:
I just wanted to let you know of a problem with the temp folder and MenuEverywhere. It seems that when MenuEverywhere starts up at login, some applications that use the system temp folder have a problem: the temp folder is cleared a few minutes after they start. If MenuEverywhere is started after these programs the problem doesn’t occur, so the fix is to not launch it at startup or not run it at all (I would miss it).
I’ve noticed this with both Microsoft Word 11 and Syntevo SmartGit 3 — it took me forever to track down MenuEverywhere as the problem, but it’s definite.
I’m running version 1.9.9 (1806) on OS X Lion 10.7.5.
On my mac the cleared folder is:
which is the tmpdir…
…and seems to be deleted and immediately reopened about 2 minutes after Smartgit or Word startup.
See this thread too:
“I found the problem. I was using the program MenuEverywhere because I have multiple monitors. I disabled MenuEverywhere, deleted it from my computer, restarted my Mac and the problem was gone. Word works again. “
I copied this message to Syntevo support, since this is a problem that seems to have come up more than once for them and I’ve been fighting it for months.
From time to time we are asked why SmartGit does not support the git rebase -p option. I’ve now tried to rebase my master which contains a merge commit onto a tiny fork ‘test‘ from an older version of master. This is the resulting log graph:
There have been a couple of modified files in my merge commit, probably due to conflicts which we had at the time or merging:
Now, a ‘git rebase -p test master‘ fails at the merge commit and results in following unexpected conflicts (at least from my perspective, as an advanced Git user):
For this reason, we decided to not support -p for rebase until now. For SmartGit 4 we will detect whether merge commits will be affected by the rebase on Pull and will suggest to merge instead, but still offer to rebase -p as well.
A few comments from us:
- at 3:10 you rather should use Graph|Select Branches (or the triangle button right beside the coloring combobox) to show non-current branches; Query|Load All Commits is meant to be used for loading (“dead-end”) commits which are not referenced by a branch or tag
- at 4:04 you don’t have to stage changed with SmartGit; instead you also can commit them directly