extensions: recommend against using wrapfunction for repo methods
Instead, all extensions should use the "dynamic subclass" trick:
subclass repo.__class__ and then replace repo.__class__ with your new
subclass. This avoids conflicts that happen when one extension uses
wrapfunction and another uses subclassing to extend the same method of
localrepository.
#!/bin/sh
# http://mercurial.selenic.com/bts/issue352
"$TESTDIR/hghave" eol-in-paths || exit 80
echo % test issue352
hg init foo
cd foo
A=`printf 'he\rllo'`
echo foo > "$A"
hg add
hg ci -A -m m
rm "$A"
echo foo > "hell
o"
hg add
hg ci -A -m m
echo foo > "$A"
hg debugwalk
# http://mercurial.selenic.com/bts/issue2036
cd ..
echo % test issue2039
hg init bar
cd bar
echo "[extensions]" >> $HGRCPATH
echo "color=" >> $HGRCPATH
A=`printf 'foo\nbar'`
B=`printf 'foo\nbar.baz'`
touch "$A"
touch "$B"
hg status --color=always
exit 0