templatekw: compare target context and its parent exactly (issue4690) Before this patch, template keywords `{file_mods}`, `{file_adds}` and `{file_dels}` use values gotten by `repo.status(ctx.p1().node(), ctx.node())`. But this doesn't work as expected if `ctx` is `memctx` or `workingcommitctx`. Typical case of templating with these contexts is customization of the text shown in the commit message editor by `[committemplate]` configuration. In this case, `ctx.node()` returns None and it causes comparison between `ctx.p1()` and `workingctx`. `workingctx` lists up all changed files in the working directory even at selective committing. BTW, `{files}` uses `ctx.files()` and it works as expected. To compare target context and its parent exactly, this patch passes `ctx.p1()` and `ctx` without `node()`-nize. This avoids unexpected comparison with `workingctx`. This patch uses a little redundant template configurations in `test-commit.t`, but they are needed to avoid regression around problems fixed by a4958cdb2202 and 1e6fb8db666e: accessing on `ctx` may break `ctx._status` field.

     1

Just exercise debugindexdot

     2

Create a short file history including a merge.

     3

  $ hg init t

     4

  $ cd t

     5

  $ echo a > a

     6

  $ hg ci -qAm t1 -d '0 0'

     7

  $ echo a >> a

     8

  $ hg ci -m t2 -d '1 0'

     9

  $ hg up -qC 0

    10

  $ echo b >> a

    11

  $ hg ci -m t3 -d '2 0'

    12

  created new head

    13

  $ HGMERGE=true hg merge -q

    14

  $ hg ci -m merge -d '3 0'

    15

    16

  $ hg debugindexdot .hg/store/data/a.i

    17

  digraph G {

    18

  	-1 -> 0

    19

  	0 -> 1

    20

  	0 -> 2

    21

  	2 -> 3

    22

  	1 -> 3

    23

  }

    24

    25

  $ cd ..