fix a9067868a8594577ead2ecbe55f9563bef12f26d to handle annexed files in conflicted merge

In the case of a conflicted merge where the remote adds a directory, and we
have a file (which is checked in), resolveMerge' will create the link,
and so the fix for a9067868a8594577ead2ecbe55f9563bef12f26d looked at that,
thought it was an unannexed file (it's not in the oldref), and preserved
it.

This is a hacky fix. It would be better for resolveMerge' to not update the
work tree, at least in direct mode, and only stage the changes, which
mergeDirectCleanUp could then move into tree. I want to make that change,
but this is not the time to do it.

0 files changed, 0 insertions, 0 deletions