Git Diff: Comparing Repository States Quiz

Review

1. What does plain `git diff` compare by default?

   Plain `git diff` compares the working tree with the index.
2. What does `git diff --cached` inspect by default?

   The cached form compares the index with HEAD by default.
3. After a change is staged and the file is edited again, where is the later edit visible?

   The second edit is in the working tree but not the index, so plain `git diff` reports it.
4. What does `git diff HEAD` provide in the ordinary local workflow?

   With HEAD as the commit side, Git reports the local content differences relative to HEAD.
5. What does `git diff HEAD~1 HEAD` compare?

   Both arguments identify commits, so Git compares their recorded trees.
6. What does `git diff -- README.md` do?

   The `--` separates revision/options from pathspecs and limits the comparison.
7. In ordinary patch output, what does a `+` line represent?

   Patch output uses `+` for content on the new side.
8. What does `--name-status` primarily provide?

   `--name-status` summarizes changed paths and their status.
9. Which statement about ordinary `git diff` is correct?

   Ordinary diff commands inspect differences; they do not stage or commit them.
10. Which command directly inspects what is staged relative to HEAD?

    `git diff --cached` compares the index with HEAD by default.