author | Petr Baudis <pasky@suse.cz> | |
Wed, 16 Jul 2008 12:35:22 +0000 (14:35 +0200) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 16 Jul 2008 15:50:07 +0000 (08:50 -0700) | ||
commit | 8bd867ee0e9714457e5ea973849b0025f3e99efc | |
tree | 0773146a7218533c24250b776c8ac0a5513b6a10 | tree | snapshot |
parent | 191a8e32b38c7ff0dd884df7bd323b7a5bd4336c | commit | diff |
Documentation/git-cherry-pick.txt et al.: Fix misleading -n description
The manual page of git-cherry-pick and git-revert asserts that -n works
primarily on the working tree, while in fact the primary object it operates
on is the index, and the changes only "accidentally" propagate to the
working tree. This e.g. leads innocent #git IRC folks to believe that you
can use -n to prepare changes for git-add -i staging.
Signed-off-by: Petr Baudis <pasky@suse.cz>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The manual page of git-cherry-pick and git-revert asserts that -n works
primarily on the working tree, while in fact the primary object it operates
on is the index, and the changes only "accidentally" propagate to the
working tree. This e.g. leads innocent #git IRC folks to believe that you
can use -n to prepare changes for git-add -i staging.
Signed-off-by: Petr Baudis <pasky@suse.cz>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-cherry-pick.txt | diff | blob | history | |
Documentation/git-revert.txt | diff | blob | history |