Thread (4 messages) 4 messages, 3 authors, 2016-06-15

Re: Mistake in git-reset documentation

From: Jeff King <hidden>
Date: 2016-06-15 22:55:08

On Sun, Oct 28, 2012 at 09:36:10AM +0100, Krzysztof Mazur wrote:
-- >8 --
Subject: [PATCH] doc: git-reset: make "--<mode>" optional

The git-reset's "--<mode>" is an optional argument, however it was
documented as required.

Signed-off-by: Krzysztof Mazur <redacted>
I think this is sane, but...
quoted hunk ↗ jump to hunk
 DESCRIPTION
 -----------
@@ -43,7 +43,7 @@ This means that `git reset -p` is the opposite of `git add -p`, i.e.
 you can use it to selectively reset hunks. See the ``Interactive Mode''
 section of linkgit:git-add[1] to learn how to operate the `--patch` mode.
 
-'git reset' --<mode> [<commit>]::
+'git reset' [--<mode>] [<commit>]::
 	This form resets the current branch head to <commit> and
 	possibly updates the index (resetting it to the tree of <commit>) and
 	the working tree depending on <mode>, which
Should we say something like "if --<mode> is omitted, defaults to
"--mixed"?

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help