On Thu, Feb 17, 2022 at 5:52 PM Julian Foad <julianf...@apache.org> wrote: > > Mark Phippard wrote: > >> | update/switch | Always | Always + Hydrate | > > > >Can you expand on this one a bit? I presume what you mean is if you > >have local mods to a file and run update/switch and there is a newer > >revision of the file in the repository it will hydrate that new > >version? But otherwise, I assume just running update does not create > >pristines. > Let's delete the word "Always" from both columns. > > Update starts by hydrating. That means it WILL download any missing pristines > of modified files, regardless whether any newer revision will be found.
Does the possibility exist to optimize this at all? Say I am working on a large binary that I have edited. My colleague checks in a different file that I want to look at so I run update. Now SVN is going to unnecessarily download another copy of that large binary. The WC knows the revision, I do not see why it would download the file from the server on update if it is not a newer version. Mark
