On Wed, Feb 16, 2022 at 4:16 AM Julian Foad <julianf...@apache.org> wrote:
> "The core idea is that we start to maintain the following invariant: only the > modified files have their pristine text-base files available on the disk." > (https://svn.apache.org/repos/asf/subversion/branches/pristines-on-demand-on-mwf/BRANCH-README) That was where I read it! thanks So this text confuses me and makes me assume I am not reading it correctly. Suppose I use this new feature to checkout a new WC without any pristines. I make edits to a large binary file using some tool. At this point, SVN does not even know I have done anything so I still have no pristines. If I run svn status it will show me the file is modified. Are you saying that when I do this, SVN is going to pull down a pristine from the server? That seems very unlikely to me but I cannot otherwise imagine what your wording in the BRANCH-README would be describing. My assumption is that if I have one of these new types of WC's that I will NEVER have any "pristines". Please enlighten me as to when pristines will be created and stored and why I would want SVN to do that when I asked for no pristines? I think I must be overlooking something obvious. Mark
