Merge branch 'ss/commit-dry-run-resolve-merge-to-no-op'
commit9ce2824e4ba56bf0f2017a0e351fa35c22a705ac
authorJunio C Hamano <gitster@pobox.com>
Mon, 23 May 2016 21:54:28 +0000 (23 14:54 -0700)
committerJunio C Hamano <gitster@pobox.com>
Mon, 23 May 2016 21:54:28 +0000 (23 14:54 -0700)
tree799aa15994da31edcbd4dc6b79a3c4b3e6458ac9
parent3916adf9978b020f9a9b165f4c1c109046899560
parent8dc874b2ee61f0c457c4482ed2f202cac55b52ad
Merge branch 'ss/commit-dry-run-resolve-merge-to-no-op'

"git commit --dry-run" reported "No, no, you cannot commit." in one
case where "git commit" would have allowed you to commit, and this
improves it a little bit ("git commit --dry-run --short" still does
not give you the correct answer, for example).  This is a stop-gap
measure in that "commit --short --dry-run" still gives an incorrect
result.

* ss/commit-dry-run-resolve-merge-to-no-op:
  wt-status.c: set commitable bit if there is a meaningful merge.
t/t7501-commit.sh
wt-status.c