We should probably be passing in a uipathfn here instead, so the
caller can get consistent output (between match.badfn and whatever
else it prints). I think we should ideally remove the badfn from the
matcher completely, but that's a different story. This patch is at
least not making it worse.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers - Commits
- rHG0ed7a8ac5711: scmutil: respect ui.relative-paths in default match.badfn
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Lint Skipped - Unit
Unit Tests Skipped