subrepo: check phase of state in each subrepositories before committing Before this patch, phase of newly created commit is determined by "phases.new-commit" configuration regardless of phase of state in each subrepositories. For example, this may cause the "public" revision in the parent repository referring the "secret" one in subrepository. This patch checks phase of state in each subrepositories before committing in the parent, and aborts or changes phase of newly created commit if subrepositories have more restricted phase than the parent. This patch uses "follow" as default value of "phases.checksubrepos" configuration, because it can keep consistency between phases of the parent and subrepositories without breaking existing tool chains.

     1

running: init test1

     2

result: None

     3

running: add foo

     4

result: 0

     5

running: commit -m commit1 -d 2000-01-01 foo

     6

result: None

     7

running: commit -m commit2 -d 2000-01-02 foo

     8

result: None

     9

running: log -r 0

    10

changeset:   0:0e4634943879

    11

user:        test

    12

date:        Sat Jan 01 00:00:00 2000 +0000

    13

summary:     commit1

    14

    15

result: None

    16

running: log -r tip

    17

changeset:   1:45589e459b2e

    18

tag:         tip

    19

user:        test

    20

date:        Sun Jan 02 00:00:00 2000 +0000

    21

summary:     commit2

    22

    23

result: None