Stephen J. Turnbull wrote:
Note that Bazaar is currently discussing some similar policies. I think the name they have settled on is ".bzrrules". Maybe .hgrules is a better name.
So it would be .hgrules/<extensionname>? With the extension then defining the contents of the rule file? An alternative would be to go one level deeper and have: .hgrules/required/<extensionname> .hgrules/optional/<extensionname> If an extension rule file appeared in the first subdirectory then hg would refuse to operate on the repository without that extension being enabled. I guess something like that might be nice to have, but the support for negative filtering and versioned rule definitions is all we really need from a python-dev point of view. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia ---------------------------------------------------------------