3 ms·
What makes git really complicated is that for every command you type, there are two things that may be affected: * the working copy * the graph And it gets b
by gerbilly 5y ago
What makes git really complicated is that for every command you type, there are two things that may be affected:
* the working copy
* the graph
And it gets better, if any file gets disconnected from the graph, it can be hard to locate. (Yes I know, it can be found in the reflog)
- rags2riches 5y agoLet's not forget about the index. Or is it called the staging area?
- RichardCA 5y agoThis conceptual overloading of language can be traced back to Linus' first commit. https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23ca2e25604af290 https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23... The original idea was "current directory cache" and that still pops up in the syntax. I always run "git diff --cached" as a last sanity check before a commit.