git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 1/5] Documentation/git-reset: reorder modes for soft-mixed-hard progression

From
Thomas Rast <trast@student.ethz.ch>
Date
Jul 18, 2010, 18:23 UTC
Message-ID
<e1b0c4024710394a5c9787c95f479a827ba18591.1279477130.git.trast@student.ethz.ch>
In-Reply-To
<cover.1279477130.git.trast@student.ethz.ch>

Reorder the documetation so that the soft/mixed/hard modes are in this order. This way they form a natural progression towards changing more of the state.

Signed-off-by: Thomas Rast <trast@student.ethz.ch>
---
 Documentation/git-reset.txt |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt
index 645f0c1..dbb810d 100644
--- a/Documentation/git-reset.txt
+++ b/Documentation/git-reset.txt
@@ -8,7 +8,7 @@ git-reset - Reset current HEAD to the specified state
 SYNOPSIS
 --------
 [verse]
-'git reset' [--mixed | --soft | --hard | --merge | --keep] [-q] [<commit>]
+'git reset' [--soft | --mixed | --hard | --merge | --keep] [-q] [<commit>]
 'git reset' [-q] [<commit>] [--] <paths>...
 'git reset' --patch [<commit>] [--] [<paths>...]
 
@@ -31,17 +31,17 @@ HEAD.
 
 OPTIONS
 -------
---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
 	requires them to be in a good order. 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::
 	Matches the working tree and index to that of the tree being
 	switched to. Any changes to tracked files in the working tree
-- 
1.7.2.rc3.317.gc287
Previous: Thomas RastNext: Thomas Rast
Message 6 of 14 in “git-reset documentation changes”
  1. 0/5 git-reset documentation changesThomas Rast, Jul 16, 2010
  2. 1/5 Documentation/git-reset: reorder modes for soft-mixed-hard progressionThomas Rast, Jul 16, 2010
  3. 2/5 Documentation/reset: separate options by modeThomas Rast, Jul 16, 2010
  4. Junio C HamanoJul 16, 2010
  5. 0/5 git-reset documentation changesThomas Rast, Jul 18, 2010
  6. 1/5 Documentation/git-reset: reorder modes for soft-mixed-hard progressionThomas Rast, Jul 18, 2010
  7. 2/5 Documentation/reset: separate options by modeThomas Rast, Jul 18, 2010
  8. 3/5 Documentation/reset: promote 'examples' one section upThomas Rast, Jul 18, 2010
  9. 4/5 Documentation/reset: reorder examples to match descriptionThomas Rast, Jul 18, 2010
  10. 5/5 Documentation/reset: move "undo permanently" example behind "make topic"Thomas Rast, Jul 18, 2010
  11. 3/5 Documentation/reset: promote 'examples' one section upThomas Rast, Jul 16, 2010
  12. 4/5 Documentation/reset: reorder examples to match descriptionThomas Rast, Jul 16, 2010
  13. 5/5 Documentation/reset: move "undo permanently" example behind "make topic"Thomas Rast, Jul 16, 2010
  14. Junio C HamanoJul 16, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.