public/git-how.md
... ...
@@ -8,8 +8,13 @@ In my opinion, the reason Git is so hard is that the commands (`git add`, `git c
8 8
have names whose semantics seem to be mapped onto the history of a variety of versioning tools, especially Subversion. The actual git commands, however, have behaviors with very precise meanings regarding specific git entities. For instance, `git add` means: Compress the files and add them to a git-managed directory, and add references to those files to the binary "index" file. Even when the official Git docs use the language of the implementation (for instance, we are told by `git help add` that `git-add` means "Add file contents to the index") it isn't very clear what
9 9
"index" means in this context. A lot would be gained by banning words such as "staging area" and "cache" and just sticking with "index."
10 10
11
+## Part 1: Git Objects
12
+
11 13
### To get started
12 14
15
+To provide visibility into what git is doin, it can help to see dynamically how directories and files are being
16
+created.
17
+
13 18
Create a couple of extra terminal tabs, and in the second tab,
14 19
15 20
watch-do $HOME/src/wiki $HOME/src/wiki "tree -t -r -C -a ."