3 ms·

I weep for the world now that git is too difficult to understand. It used to explain itself through building your own version of git. You have a file named has

I weep for the world now that git is too difficult to understand. It used to explain itself through building your own version of git. You have a file named hash that tracks changes on each file named foo... now all the changes are in a directory named hash...now your changes have to be merged with others... It's kind of up there with next steps after if then else fi. Some things will always be difficult, but diffs and commit and picking one of two possible diffs from two windows should not be one of them.

Bigpet 5y ago
The issue is not really the base concept. It's layering a huge amount of concepts on top of it. Just think of the "places" a change can be in (technically most of these are just labels on the tree, but they have separate commands to deal with them). Remote, Index, working copy, staging area, stash, branches. Those are the ones involved in the simples way I know how to make the smallest change. When you get up to stuff like submodules, LFS, subtrees then I very much understand when people get frustrated. All most of them wanted is a slight improvement over copying a folder they named myproject_v23 to a network drive.