On Thu, Feb 17, 2022 at 9:41 AM Julian Foad <jul...@foad.me.uk> wrote: > > Mark Phippard wrote: > [...] > >currently there is no pristine. Now I run svn diff and I see the > >result. The command ends ... there is still no pristine. [...] If, when the > >command finishes, there are no pristines stored on disk ... then there > >are no pristines. > The bit you are missing is, at the end of a diff command, the diffed file is > still locally modified so the pristine is not felted then, it is kept in the > store indefinitely. Only when some subsequent command finds it unmodified, > only then will it be removed. (No matter whether it became unmodified by an > svn operation such as revert or commit, in which case the command that did > that would have removed the pristine; or if it was reverted by the user > without involving svn.) > > I agree about the insufficiency of current docs and how the commands could be > listed in full.
Thanks Julian, that is clearer. FWIW, this is the wording that confused me: "The operations also include a final step during which the no longer required text-bases are removed from disk" The use of "the operations" made me think it was the same operation. IOW, I read this as the "diff operation" includes a final step that does this cleanup. What you seem to be saying is some other future operation like revert or commit is what would clean it up. I agree this is a reasonable way for the feature to behave BTW. At least assuming there are no "surprises" about what operations trigger the need to fetch the pristine. Mark
