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
# Some tests for hgweb in an empty repository
hg init test
cd test
hg serve -n test -p $HGPORT -d --pid-file=hg.pid -A access.log -E errors.log
cat hg.pid >> $DAEMON_PIDS
("$TESTDIR/get-with-headers.py" localhost:$HGPORT '/shortlog')
("$TESTDIR/get-with-headers.py" localhost:$HGPORT '/log')
("$TESTDIR/get-with-headers.py" localhost:$HGPORT '/graph')
("$TESTDIR/get-with-headers.py" localhost:$HGPORT '/file')