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

Test the GPG extension

     2

     3

  $ "$TESTDIR/hghave" gpg || exit 80

     4

  $ cat <<EOF >> $HGRCPATH

     5

  > [extensions]

     6

  > gpg=

     7

  > 

     8

  > [gpg]

     9

  > cmd=gpg --no-permission-warning --no-secmem-warning --no-auto-check-trustdb --homedir "$TESTDIR/gpg"

    10

  > EOF

    11

  $ hg init r

    12

  $ cd r

    13

  $ echo foo > foo

    14

  $ hg ci -Amfoo

    15

  adding foo

    16

    17

  $ hg sigs

    18

    19

  $ hg sign 0

    20

  signing 0:e63c23eaa88a

    21

    22

  $ hg sigs

    23

  hgtest                             0:e63c23eaa88ae77967edcf4ea194d31167c478b0

    24

    25

  $ hg sigcheck 0

    26

  e63c23eaa88a is signed by:

    27

   hgtest

    28

    29

verify that this test has not modified the trustdb.gpg file back in

    30

the main hg working dir

    31

  $ "$TESTDIR/md5sum.py" "$TESTDIR/gpg/trustdb.gpg"

    32

  f6b9c78c65fa9536e7512bb2ceb338ae  */gpg/trustdb.gpg (glob)

    33

    34

  $ cd ..