From 01997b4a256ed7ef96ede527a92eeeecc243a927 Mon Sep 17 00:00:00 2001 From: "J. Bruce Fields" Date: Wed, 10 Jan 2007 23:23:37 -0500 Subject: [PATCH] user manual: answer some comments from Junio Junio left a few comments in his previous patch; deal with each of them. Signed-off-by: J. Bruce Fields --- Documentation/user-manual.txt | 33 ++++++++++----------------------- 1 file changed, 10 insertions(+), 23 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 7cd4dd6ab0..ae21ef239e 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -863,17 +863,10 @@ times as you want: in order to keep track of what you want committed at step 3, git maintains a snapshot of the tree's contents in a special staging area called "the index." -By default, the content of the index is identical to that of the -HEAD. The command "git diff --cached" shows the difference between -HEAD and the index, so you should no output from that command. - -//////////////////////////////////////////////// - -This is talking about not "by default", but "when you start -out". The last sentence does not parse for me... - -//////////////////////////////////////////////// - +At the beginning, the content of the index will be identical to +that of the HEAD. The command "git diff --cached", which shows +the difference between the HEAD and the index, should therefore +produce no output at that point. Modifying the index is easy: @@ -1337,20 +1330,14 @@ single mailbox file, say "patches.mbox", then run $ git am -3 patches.mbox ------------------------------------------------- -//////////////////////////////////////////////// - -If you allow git-am to fall back to 3-way merge with -3, you -would see conflicts and "resolving a merge" techniques apply. -Otherwise "conflicts" will just fail the patch and your working -tree and index are left untouched. - -//////////////////////////////////////////////// - Git will apply each patch in order; if any conflicts are found, it will stop, and you can fix the conflicts as described in -"<>". Once the index is updated -with the results of the conflict resolution, instead of creating a -new commit, just run +"<>". (The "-3" option tells +git to perform a merge; if you would prefer it just to abort and +leave your tree and index untouched, you may omit that option.) + +Once the index is updated with the results of the conflict +resolution, instead of creating a new commit, just run ------------------------------------------------- $ git am --resolved -- 2.11.4.GIT