merge: store commitinfo if these is a dc or cd conflict delete-changed or changed-delete conflicts can either be resolved by mergetool, if some tool is passed and using or by user choose something on prompt or user doing some `hg revert` after choosing the file to remain conflicted. If the user decides to keep the changed side, on commit we just reuse the parent filenode. This is mostly fine unless we are in a distributed environment and people are doing criss-cross merges. Since, we don't have recursive merges or any other way of describing the end result of the merge was an explicit choice and it should be differentiated from it's ancestors, merge algo during criss-cross merges fails to take in account the explicit choice made by user and end up with a what-can-be-said-wrong-merge. The solution which we are trying to fix this is by creating a filenode on commit instead of reusing the parent filenode. This helps differentiate between pre-merged filenode and post-merge filenode and kind of tells about the choice user made. To implement creating new filenode functionality, we store info about these files in mergestate so that we can read them on commit and force create a new filenode. Differential Revision: https://phab.mercurial-scm.org/D8988

     1

#require execbit

     2

     3

  $ hg init

     4

  $ echo a > a

     5

  $ hg ci -Am'not executable'

     6

  adding a

     7

     8

  $ chmod +x a

     9

  $ hg ci -m'executable'

    10

  $ hg id

    11

  79abf14474dc tip

    12

    13

Make sure we notice the change of mode if the cached size == -1:

    14

    15

  $ hg rm a

    16

  $ hg revert -r 0 a

    17

  $ hg debugstate

    18

  n   0         -1 unset               a

    19

  $ hg status

    20

  M a

    21

    22

  $ hg up 0

    23

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    24

  $ hg id

    25

  d69afc33ff8a

    26

  $ test -x a && echo executable -- bad || echo not executable -- good

    27

  not executable -- good

    28