On Sat, Feb 12, 2022 at 3:15 PM Karl Fogel <kfo...@red-bean.com> wrote:
> The name of the "pristines-on-demand" branch implies a certain > behavior -- namely, that pristines can, via some UI, be fetched on > demand :-). But in the MVP we're talking about, pristines in a > given WC are either all present or all absent, and, at least for > MVP, that per-WC state is not changeable, right? Just to offer a counterpoint Karl, I always assumed the goal of the branch was to have no pristines in the WC and the "on-demand" aspect was referring to an internal SVN detail that it would have to fetch pristines when they were needed to complete a command that I have executed like diff or revert. I know we discussed whether the entire WC, or individual files would not have pristines but I never considered the "on-demand" aspect to be about my ability to decide this. It was about SVN just doing what it needed to when it needed to. Mark
