topic: drop support for accessing csets in branch stack using bxx (issue6119) When topic extension is enabled and we have some cset whose hash is `b1234`, topic extension thinks that we are accessing 1234 cset in current branch stack. However that's not the case generally. Also I am not sure many people use this bxxx thing. Since we have a generic sxxx way to access csets, let's drop support for accessing csets using bxx which leads to bad behavior. Looking at the tests, we don't show bxxx in hg stack output anymore. I update the test to use sxxx instead of bxxxx.

     1

Test that share-clones use the cache in the original repository.

     2

     3

  $ . $TESTDIR/testlib/common.sh

     4

     5

  $ hg init share-base

     6

  $ cd share-base/

     7

  $ cat >> .hg/hgrc <<EOF

     8

  > [extensions]

     9

  > evolve=

    10

  > share=

    11

  > EOF

    12

  $ hg debugbuilddag .+3:branchpoint+4*branchpoint+2

    13

  $ cd ..

    14

  $ hg --config extensions.share= share -U share-base share-client

    15

  $ cd share-client

    16

  $ hg debugupdatecache

    17

  $ test -d .hg/cache

    18

  [1]

    19

  $ test -d ../share-base/.hg/cache

    20