summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes-1.6.2.5.txt
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2010-06-06 20:41:46 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2010-06-11 08:55:57 -0700
commitf197ed2fbeb2868c3514ad35bf986a3aa60285f0 (patch)
treede39fff1a675df503380579b4a178dc0003a63d5 /Documentation/RelNotes-1.6.2.5.txt
parentChange C99 comments to old-style C comments (diff)
downloadtgif-f197ed2fbeb2868c3514ad35bf986a3aa60285f0.tar.xz
commit: give advice on empty amend
We generally disallow empty commits with "git commit". The output produced by the wt_status functions is generally sufficient to explain what happened. With --amend commits, however, things are a little more confusing. We would create an empty commit not if you actually have staged changes _now_, but if your staged changes match HEAD^. In this case, it is not immediately obvious why "git commit" claims no changes, but "git status" does not. Furthermore, we should point the user in the direction of git reset, which would eliminate the empty commit entirely. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes-1.6.2.5.txt')
0 files changed, 0 insertions, 0 deletions