repoview: introduce a `experimental.extra-filter-revs` config The option define revisions to additionally filter out of all repository "view". The end goal is to provide and easy to way to serve multiple subset of the same repository using multiple "shares". The simplest use case of this feature is to have one view serving the public changesets and one view also serving the draft. This is currently achievable using the new `server.view` option introduced recently by Joerg Sonnenberger. However, more advanced use cases need more advanced definitions. For example some needs a view dedicated to some release branches, or view that hides security fixes to be released. Joerg Sonnenberger and I discussed this topic at the recent mini-sprint and the both of us have seen real life use cases for this. (This series got written during the same mini-sprint). The feature is fully functional, and use similar cache-fallback mechanism to ensure decent performance. However,there remaining room to ensure each share caches and hooks collaborate with each others. This will come at a later time once users start to actually test this feature on real usecase.

     1

  $ hg init test

     2

  $ cd test

     3

  $ hg debugbuilddag '+2'

     4

  $ hg phase --public 0

     5

     6

  $ hg serve -p $HGPORT -d --pid-file=hg.pid -E errors.log

     7

  $ cat hg.pid >> $DAEMON_PIDS

     8

  $ cd ..

     9

  $ hg init test2

    10

  $ cd test2

    11

  $ hg incoming http://foo:xyzzy@localhost:$HGPORT/

    12

  comparing with http://foo:***@localhost:$HGPORT/

    13

  changeset:   0:1ea73414a91b

    14

  user:        debugbuilddag

    15

  date:        Thu Jan 01 00:00:00 1970 +0000

    16

  summary:     r0

    17

    18

  changeset:   1:66f7d451a68b

    19

  tag:         tip

    20

  user:        debugbuilddag

    21

  date:        Thu Jan 01 00:00:01 1970 +0000

    22

  summary:     r1

    23

    24

  $ killdaemons.py

    25

    26

  $ cd ..

    27

  $ hg -R test --config server.view=immutable serve -p $HGPORT -d --pid-file=hg.pid -E errors.log

    28

  $ cat hg.pid >> $DAEMON_PIDS

    29

  $ hg -R test2 incoming http://foo:xyzzy@localhost:$HGPORT/

    30

  comparing with http://foo:***@localhost:$HGPORT/

    31

  changeset:   0:1ea73414a91b

    32

  tag:         tip

    33

  user:        debugbuilddag

    34

  date:        Thu Jan 01 00:00:00 1970 +0000

    35

  summary:     r0

    36

    37

    38

Check same result using `experimental.extra-filter-revs`

    39

    40

  $ hg -R test --config experimental.extra-filter-revs='not public()' serve -p $HGPORT1 -d --pid-file=hg2.pid -E errors.log

    41

  $ cat hg2.pid >> $DAEMON_PIDS

    42

  $ hg -R test2 incoming http://foo:xyzzy@localhost:$HGPORT1/

    43

  comparing with http://foo:***@localhost:$HGPORT1/

    44

  changeset:   0:1ea73414a91b

    45

  tag:         tip

    46

  user:        debugbuilddag

    47

  date:        Thu Jan 01 00:00:00 1970 +0000

    48

  summary:     r0

    49

    50

  $ hg -R test --config experimental.extra-filter-revs='not public()' debugupdatecache

    51

  $ ls -1 test/.hg/cache/

    52

  branch2-base%89c45d2fa07e

    53

  branch2-served

    54

  rbc-names-v1

    55

  rbc-revs-v1

    56

  tags2

    57

  tags2-served%89c45d2fa07e

    58

    59

cleanup

    60

    61

  $ cat errors.log

    62

  $ killdaemons.py