filemerge: when using in-memory merge, always put backup files in temp dir Before calling a merge tool, we create a backup of the local side of the merge. That file can be put in the working copy or in a temporary directory, depending on the user's config. When we're merging in memory, we don't want to write to the actual, on-disk working copy, so we write the file to the in-memory working copy instead. However, since we don't support external merge tools with in-memory merge, it makes no difference where the file is actually stored (and if we ever do add support for external merge tools, then the file clearly can't live in the in-memory working-copy object anyway). So, since it doesn't matter where the file is stored, we can simplify by always putting them in the system's temp directory. Differential Revision: https://phab.mercurial-scm.org/D12187

     1

Test null revisions (node 0000000000000000000000000000000000000000, aka rev -1)

     2

in various circumstances.

     3

     4

Make an empty repo:

     5

     6

  $ hg init a

     7

  $ cd a

     8

     9

  $ hg files -r 0000000000000000000000000000000000000000

    10

  [1]

    11

  $ hg files -r .

    12

  [1]

    13

    14

Add an empty commit (this makes the changelog refer to a null manifest node):

    15

    16

    17

  $ hg commit -m "init" --config ui.allowemptycommit=true

    18

    19

  $ hg files -r .

    20

  [1]

    21

    22

Strip that empty commit (this makes the changelog file empty, as opposed to missing):

    23

    24

  $ hg --config 'extensions.strip=' strip . > /dev/null

    25

    26

  $ hg files -r .

    27

  [1]