view rust/Cargo.toml @ 39768:7b2b42fc377a

revlog: store flag processors per revlog Previously, revlog flag processing would consult a global dict when processing flags. This was simple. But it had the undesired side-effect that any extension could load flag processors once and those flag processors would be available to any revlog that was subsequent loaded in the process. e.g. in hgweb, if the narrow extension were loaded for repo A but not repo B, repo B would be able to decode ellipsis flags even though it shouldn't be able to. Making the flag processors dict per-revlog allows us to have per-revlog controls over what flag processors are available, thus preserving desired granular access to flag processors depending on the revlog's needs. If a flag processor is globally registered, it is still globally available. So this commit should not meaningfully change behavior. Differential Revision: https://phab.mercurial-scm.org/D4646
author Gregory Szorc <gregory.szorc@gmail.com>
date Thu, 13 Sep 2018 15:48:53 -0700
parents 964212780daf
children aab43d5861bb
line wrap: on
line source

[workspace]
members = ["hgcli"]