First, thanks for releasing this! I've been getting by with a blend of gitg, IntelliJ and Git from the command line up until yesterday to reproduce my SourceTree workflow from my macOS days. :)
Problem
Seeing weird issues running Sublime Merge on CentOS 7, specifically:
- commit list is missing the branch local/remote tracking badges for repos that are definitely tracking remotes
- one repo listed 30+ files as having been modified and staged (that I hadn't actually modified or staged) while
git status reported a clean working tree. Expanding the row for each file showed the "no content" placeholder. Clicking Unstage just made the row flicker for a split second but it remained staged.
- after deleting and re-cloning the repo mentioned above, SM either crashes when I try to open it or truncates everything beneath the latest commit and lists no file changes under it
I'm assuming it's because the version of git that that ships with CentOS (1.8.x I believe) doesn't like one or more of the commands being passed to it. I'm not seeing any of those issues on my Fedora 28 machine (git 2.17.1).
Attempted fixes
- deleted
~/.config/sublime-merge/Cache a bunch of times and restarted
- deleted the files in the repo that SM was reporting and
git checkout . to pull them back
git reset --hard at the repo root
- delete entire repo from disk (deleting the SM cache folder again) and re-clone from command line (SM either crashes when I try to open the repo or truncates everything beneath the latest commit and lists no file changes under it)
First, thanks for releasing this! I've been getting by with a blend of gitg, IntelliJ and Git from the command line up until yesterday to reproduce my SourceTree workflow from my macOS days. :)
Problem
Seeing weird issues running Sublime Merge on CentOS 7, specifically:
git statusreported a clean working tree. Expanding the row for each file showed the "no content" placeholder. Clicking Unstage just made the row flicker for a split second but it remained staged.I'm assuming it's because the version of git that that ships with CentOS (1.8.x I believe) doesn't like one or more of the commands being passed to it. I'm not seeing any of those issues on my Fedora 28 machine (git 2.17.1).
Attempted fixes
~/.config/sublime-merge/Cachea bunch of times and restartedgit checkout .to pull them backgit reset --hardat the repo root