> [2] From a usability perspective, the merge state should not be written when the index is being > written (merge conflicts are not considered failures). To avoid losing changes in the source branch, "the merge state should not be written when the index is being written" should be: the merge state should not be written if the index write fails. > users can only execute 'git merge --abort' and try 'git merge' again. However, if the merge state is > not written in the first place, the user only needs to retry 'git merge'. >In other words, writing the merge state after the index write fails is meaningless and could >potentially cause Git to lose changes.
