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

     2

     3

# No local source

     4

hg clone a b

     5

echo $?

     6

     7

# No remote source

     8

hg clone http://127.0.0.1:3121/a b

     9

echo $?

    10

rm -rf b # work around bug with http clone

    11

    12

# Inaccessible source

    13

mkdir a

    14

chmod 000 a

    15

hg clone a b

    16

echo $?

    17

    18

# Inaccessible destination

    19

mkdir b

    20

cd b

    21

hg init

    22

hg clone . ../a

    23

echo $?

    24

cd ..

    25

chmod 700 a

    26

rm -rf a b

    27

    28

# Source of wrong type

    29

mkfifo a

    30

hg clone a b

    31

echo $?

    32

rm a

    33

    34

# Default destination, same directory

    35

mkdir q

    36

cd q

    37

hg init

    38

cd ..

    39

hg clone q

    40

    41

true