Use a case-sensitive version of SafeConfigParser everywhere This change has the potential to break existing setups, but the current behaviour (the keys in configuration files are always lower-cased) can bite us in a few places: - no way to use a Command in [defaults] - hgext.Extension doesn't work in [extensions] - you can't use an Upper/case/PATH in the [paths] section of hgweb.config - you can't (easily) protect paths with upper-case letters with the acl extension - you can't specify a /Path/TO/a/rEPO in the [reposubs] section for the notify extension

     1

#!/bin/sh -e

     2

     3

umask 027

     4

mkdir test1

     5

cd test1

     6

     7

hg init

     8

touch a b

     9

hg add a b

    10

hg ci -m "added a b" -d "1000000 0"

    11

    12

cd ..

    13

hg clone test1 test3

    14

mkdir test2

    15

cd test2

    16

    17

hg init

    18

hg pull ../test1

    19

hg co

    20

chmod +x a

    21

hg ci -m "chmod +x a" -d "1000000 0"

    22

    23

cd ../test1

    24

echo 123 >>a

    25

hg ci -m "a updated" -d "1000000 0"

    26

    27

hg pull ../test2

    28

hg heads

    29

hg history

    30

    31

hg -v merge

    32

    33

cd ../test3

    34

echo 123 >>b

    35

hg ci -m "b updated" -d "1000000 0"

    36

    37

hg pull ../test2

    38

hg heads

    39

hg history

    40

    41

hg -v merge

    42

    43

ls -l ../test[123]/a > foo

    44

cut -b 1-10 < foo

    45

    46

hg debugindex .hg/data/a.i

    47

hg debugindex ../test2/.hg/data/a.i

    48

hg debugindex ../test1/.hg/data/a.i