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
hg init
echo a > a
hg add
hg ci -m1
# set mtime of a into the future
touch -t 202101011200 a
# status must not set a's entry to unset (issue1790)
hg status
hg debugstate