Once a user starts performing merges and trying to fix conflicts by hand, simplicity goes out the windows. It’s not git, but any tree system that has to track and merge content. Same thing would happen with any other tool if the user is trying to “recreate” revisions that had bad merges.
The thread reads like Git is just as awesome to use as one would suspect from the outside, even for the original target audience.
Once a user starts performing merges and trying to fix conflicts by hand, simplicity goes out the windows. It’s not git, but any tree system that has to track and merge content. Same thing would happen with any other tool if the user is trying to “recreate” revisions that had bad merges.
A script called b4 was at fault but sure blame git
More like git blame amiright?!
fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).(u r not rite)