Share your ideas on how to improve SmartGit!
This is no support platform! To report bugs or request support, please contact us directly. If in doubt ask us.
First search for a similar request and add your votes or comments there.
Take the time to describe your request as precise as possible, so we (Syntevo) and other users will understand what you want. A plain request "SmartGit should look cool" is too vague because we don't know what we should change, and hence will not be approved by us.
Thank you for your help!
Currently changes are highlighted in green background which is harder to see if you have green text around your changes. Instead, code changes should have e.g. light red highlight (similar to what Beyond Compare diffing tool does).
We have files in one repository, which are encoded in several different encodings. It would be great if we had possibility to switch their encoding setting for each file like in Eclipse.
Perhaps, encoding could also be detected automatically.
When you clone a new repo and pick a project from Github, the Github Projects window should display a progress indicator while loading the list of projects. Currently it just displays an empty list for a couple of seconds, which gives the impression that there are no projects available.
The .gitsvnextmodules that refer to regular Git repositories are being checked out as SVN, instead of regular Git submodules.
If this Git repository resides on GitHub SmartGit does not support it. (svn: E204900: Can't clone an SVN repository from GitHub. GitHub uses a non-standard SVN server and hence those repositories can't be cloned with SmartGit.)
Also there is no option to add a remote Git submodule via the GUI and the option for a local Git or Mercurial repository is greyed out.
However, adding a remote Git submodule to a SVN-Git bridge checkout via command line works and SmartGit picks it up OK.
I have remotes, which I have Write access to, that I never want to push to using SmartGit. Allow me to configure SmartGit to restrict somehow pushing to those remotes.
This does not need to apply to the command line as well.
I develop on Linux and windows the same code, so I don't really care what line endings are used where.
I do prefer to have Unix line endings everywhere because in Windows, my editor knows what to do about them but in Linux, it is better to get rid of Windows line endings.
So, I'd like to have a preference to enable one type of line ending that would be carried away to all copies of my code.
Even better option would be to have a logic that would somehow detect the line endings on the origin, and convert as I want it on local, automatically.
For example, if I create a repo and make some source files on Linux, then push it to GitHub for example, then clone it on Windows, it would be perfect if SmartGit would convert all line endings to CRLF on "download" and back to LF on "upload".
In the log view you can select a single commit and use the 'format patch' functionality to create a single patch.
However, I frequently have the need to select a range of sequential commits and make patches for each commit.
Basically the same functionality as for example 'git format-patch -3' to create 3 patches from the top 3 commits. SmartGit does not seem to provide this functionality. Why not?
Customer support service by UserEcho