[PATCHv2 1/6] git-reset.txt: clarify branch vs. branch head
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Sep 15, 2010, 20:47 UTC
- Message-ID
- <3ad8c4b01449e4d4563193bce9fd10365c59cccb.1284582409.git.git@drmicha.warpmail.net>
- In-Reply-To
- <cover.1284365021.git.git@drmicha.warpmail.net>
"Change the branch" can be misunderstood to mean "change which branch is checked out". Make it clearer that git-reset changes the branch head of the currently checked out branch.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> --- Documentation/git-reset.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt index 9cf3148..91bd2e9 100644 --- a/Documentation/git-reset.txt +++ b/Documentation/git-reset.txt @@ -15,7 +15,7 @@ SYNOPSIS DESCRIPTION ----------- In the first and second form, copy entries from <commit> to the index. -In the third form, set the current branch to <commit>, optionally +In the third form, set the current branch head to <commit>, optionally modifying index and worktree to match. The <commit> defaults to HEAD in all forms. @@ -36,7 +36,7 @@ This means that `git reset -p` is the opposite of `git add -p` (see linkgit:git-add[1]). 'git reset' [--<mode>] [<commit>]:: - This form points the current branch to <commit> and then + This form resets the current branch head to <commit> and then updates index and working tree according to <mode>, which must be one of the following: +
-- 1.7.3.rc1.215.g6997c