Slightly reword the first sentence ("you use" instead of "Git stores")
Julia Evans (2):
doc: git-add: clarify intro & add an example
doc: git-add: simplify discussion of ignored files
Documentation/git-add.adoc | 34 ++++++++++++++++------------------
1 file changed, 16 insertions(+), 18 deletions(-)
base-commit: c44beea485f0f2feaf460e2ac87fdd5608d63cf0
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1952%2Fjvns%2Fclarify-add-v4
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1952/jvns/clarify-add-v4
Pull-Request: https://github.com/gitgitgadget/git/pull/1952
Range-diff vs v3:
1: c44beea485 < -: ---------- Git 2.51
2: 080720c059 ! 1: 57947d5a3e doc: git-add: clarify intro & add an example
@@ Documentation/git-add.adoc: git add [--verbose | -v] [--dry-run | -n] [--force |
-the commit command, you must use the `add` command to add any new or
-modified files to the index.
+Add contents of new or changed files to the index. The "index" (also
-+known as "staging area") is where Git stores the contents of the next
-+commit.
++known as the "staging area") is what you use to prepare the contents of
++the next commit.
+
+When you run `git commit` without any other arguments, it will only
+commit staged changes. For example, if you've edited `file.c` and want
3: fc2ec305a9 = 2: f57effdd2b doc: git-add: simplify discussion of ignored files
--
gitgitgadget
