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.

adding a
comparing with l://
searching for changes
no changes found
% check that {1} syntax works
using http://localhost:/
sending between command
comparing with parts://localhost
sending heads command
searching for changes
no changes found
% check that paths are expanded
comparing with z://
searching for changes
no changes found
% errors