Michael J Gruber [off-list ref] writes:
quoted
The documentation of "git update-index --unresolve" lacks this info,
and it doesn't tell one what it is for (see commit message for commit
ec16779 (Add git-unresolve <paths>..., 2006-04-19)).
Oh yes, one should always read the classics ;) [Really nice commit
message, that is.]
Thanks.
This is exactly why I often give _explanation_ of the current behaviour
based on history, without defending it is good nor claiming it is bad.
Knowing how things came about gives us better perspective to decide where
to go next.