On Mon, Sep 13, 2010 at 4:06 AM, Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote: > Make it clearer that git reset --soft actually does something (changing > HEAD). While it is meantioned in the previous paragraph already it can > be easily overlooked otherwise. > > Signed-off-by: Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> > --- > Documentation/git-reset.txt | 3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt > index 8fb871c..65f5d07 100644 > --- a/Documentation/git-reset.txt > +++ b/Documentation/git-reset.txt > @@ -43,7 +43,8 @@ linkgit:git-add[1]). > -- > --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 > + requires them to be in good order (and sets 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. What does "requires them to be in good order" mean anyway? j. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html