Sourcetree is having trouble with forward slashes in the git commit messages. I'm getting error messages like the ones below when trying to view these repostories where the head commit has a forward slash.
11/4/12 12:20:27.706 AM SourceTree: 'git log' failed with code 128:'fatal: ambiguous argument 'CR/MM': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
That's strange, because I and many others use forward slashes in branch names all the time, it's not only always the case for remote branches, but when you're using git-flow, most branches have prefixes with a slash in them.
Please can you provide more details about what version of SourceTree you're using, your repo state and the gitconfig you're using (locally and globally).
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs