[PATCH] git-reset.txt: (git reset): order options alphabetically
From: <hidden>
Date: 2016-06-15 22:50:08
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
From: Jari Aalto <redacted> Signed-off-by: Jari Aalto <redacted> --- Documentation/git-reset.txt | 43 ++++++++++++++++++++++--------------------- 1 files changed, 22 insertions(+), 21 deletions(-)
diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt
index fd72976..e89956f 100644
--- a/Documentation/git-reset.txt
+++ b/Documentation/git-reset.txt@@ -49,21 +49,21 @@ linkgit:git-add[1]). must be one of the following: + -- ---soft:: - Does not touch the index file nor the working tree at all (but - resets the head to <commit>, just like all modes do). This leaves - all your changed files "Changes to be committed", as 'git status' - would put it. - ---mixed:: - Resets the index but not the working tree (i.e., the changed files - are preserved but not marked for commit) and reports what has not - been updated. This is the default action. - --hard:: Resets the index and working tree. Any changes to tracked files in the working tree since <commit> are discarded. +--keep:: + Resets the index, updates files in the working tree that are + different between <commit> and HEAD, but keeps those + which are different between HEAD and the working tree (i.e. + which have local changes). + If a file that is different between <commit> and HEAD has local changes, + reset is aborted. ++ +In other words, --keep does a 2-way merge between <commit> and HEAD followed by +'git reset --mixed <commit>'. + --merge:: Resets the index and updates the files in the working tree that are different between <commit> and HEAD, but keeps those which are
@@ -75,16 +75,17 @@ linkgit:git-add[1]). In other words, --merge does something like a 'git read-tree -u -m <commit>', but carries forward unmerged index entries. ---keep:: - Resets the index, updates files in the working tree that are - different between <commit> and HEAD, but keeps those - which are different between HEAD and the working tree (i.e. - which have local changes). - If a file that is different between <commit> and HEAD has local changes, - reset is aborted. -+ -In other words, --keep does a 2-way merge between <commit> and HEAD followed by -'git reset --mixed <commit>'. +--mixed:: + Resets the index but not the working tree (i.e., the changed files + are preserved but not marked for commit) and reports what has not + been updated. This is the default action. + +--soft:: + Does not touch the index file nor the working tree at all (but + resets the head to <commit>, just like all modes do). This leaves + all your changed files "Changes to be committed", as 'git status' + would put it. + -- If you want to undo a commit other than the latest on a branch,
--
1.7.2.3