diff options
| author | Soon Van <cog@randomecho.com> | 2013-05-22 21:56:20 +0400 |
|---|---|---|
| committer | Andrew Dailey <andrew.dailey@hotelsathome.com> | 2014-01-08 22:35:01 +0400 |
| commit | 450a1c1b1890ef519a5dc43980a2b70c2b7dda45 (patch) | |
| tree | 4e1c6a852926497fb1595215fe9d72b44a58e253 | |
| parent | 96186d05ff119871376ee81f80d9a8ef0e3c0c5a (diff) | |
Clarify where git reset moves HEAD, affect on stage, index
| -rw-r--r-- | basic/index.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/basic/index.html b/basic/index.html index 100c11d..6c765b5 100644 --- a/basic/index.html +++ b/basic/index.html @@ -691,7 +691,7 @@ M hello.rb <h4> git reset --soft - <small>moves what HEAD points to, index and staging are untouched</small> + <small>moves HEAD to specified commit reference, index and staging are untouched</small> </h4> <p>The first thing <code>git reset</code> does is undo the last @@ -753,8 +753,8 @@ nothing to commit (working directory clean) <p>In the above example, while we had both changes ready to commit and ready to stage, a <code>git reset --hard</code> wiped them out. - The working tree and stage are now reset to the point just after the - commit pointed at by HEAD.</p> + The working tree and staging area are reset to the tip of the current + branch or HEAD.</p> <p>You can replace <code>HEAD</code> with a commit SHA-1 or another parent reference to reset to that specific point.</p> |