author | Junio C Hamano <junkio@cox.net> | |
Sun, 10 Dec 2006 06:32:43 +0000 (22:32 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sun, 10 Dec 2006 22:50:40 +0000 (14:50 -0800) | ||
commit | 158d0577891441c01457bbcaf45585d3b50f5d75 | |
tree | 9e3d206e69ba0dc4869097f0c9ba270bdb970ede | tree | snapshot |
parent | 6c96753df9db7f790a2ac4d95ec2a868394cd5ff | commit | diff |
git-commit: allow --only to lose what was staged earlier.
The command used to have a safety valve to prevent this sequence:
edit foo
git update-index foo
edit foo
git diff foo
git commit --only foo
The reason for this was because an inexperienced user might
mistakenly think what is shown with the last-minute diff
contains all the change that is being committed (instead, what
the user asked to check was an incremental diff since what has
been staged so far). However, this turns out to only annoy
people who know what they are doing. Inexperienced people
would not be using the first "update-index" anyway, in which
case they would see the full changes in the "git diff".
Signed-off-by: Junio C Hamano <junkio@cox.net>
The command used to have a safety valve to prevent this sequence:
edit foo
git update-index foo
edit foo
git diff foo
git commit --only foo
The reason for this was because an inexperienced user might
mistakenly think what is shown with the last-minute diff
contains all the change that is being committed (instead, what
the user asked to check was an incremental diff since what has
been staged so far). However, this turns out to only annoy
people who know what they are doing. Inexperienced people
would not be using the first "update-index" anyway, in which
case they would see the full changes in the "git diff".
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-commit.sh | diff | blob | history |