summaryrefslogtreecommitdiff
path: root/sha256/block/sha256.c
diff options
context:
space:
mode:
authorLibravatar Nguyễn Thái Ngọc Duy <pclouds@gmail.com>2019-02-06 09:51:15 +0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-02-06 12:46:08 -0800
commit1d1f689bef77b1bd0cb0f0bc0e0bd766283c5df8 (patch)
treeae9d0724810c76ea98ca064813e8339dcd0d2626 /sha256/block/sha256.c
parentcheckout: update count-checkouts messages (diff)
downloadtgif-1d1f689bef77b1bd0cb0f0bc0e0bd766283c5df8.tar.xz
checkout: count and print -m paths separately
Since 0f086e6dca (checkout: print something when checking out paths - 2018-11-13), this command reports how many paths have been updated from what source (either from a tree, or from the index). I forget that there's a third source: when -m is used, the merge conflict is re-created (granted, also from the index, but it's not a straight copy from the index). Count and report unmerged paths separately. There's a bit more update to avoid reporting: Recreated X merge conflicts Updated 0 paths from the index The second line is unnecessary. Though if there's no conflict recreation, we still report Updated 0 paths from the index to make it clear we're not really doing anything. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'sha256/block/sha256.c')
0 files changed, 0 insertions, 0 deletions