Too many special characters in the commands. How am I supposed to keep track of what all the special characters mean? And furthermore, some special characters mean different things in different commands. For example, in some git commands, the "--" means "end of options", but in the git log command, it means to only look at the log for one file. If the commands are going to use special characters, it should at least be consistent.

The "git reset" does one of several completely different things depending on what flags you specify. For example, it can erase pending changes on a file, or it can bring the repo to a different point in its commit history. If a command can do several things that are not logically related to each other, it should be split up into different commands.

With merge conflicts, it is always a pain to try to tell it to override with respect to the remote repo or the local repo.

Configuration files within the repo are a nightmare to deal with. Yes it is easy to get it to ignore a file altogether, but it is very tricky to get it to ignore further changes to a certain file that already exists in the repo. I find the easiest way to deal with this issue is to just keep configuration files outside of the repo.

Git makes it easy to make it permanently lose data by making "git push -f" the only easy way to resolve many conflicts encountered when trying to push.

Git seems to always make the bad way of doing things easier than the good way. For example, once I remember I was trying to just revert to an earlier point in the commit history, while preserving the commits that came after it, in case I needed to refer to them at some point. I found this excessively difficult to do. I could temporarily view an earlier commit without trouble. I could also easily revert the repo to an earlier commit, but only by losing the commits after it in the process. But reverting to an earlier commit while preserving the commit history required following a complicated series of steps.