On 15 Feb 2022, Mark Phippard wrote:
On Tue, Feb 15, 2022 at 12:00 PM Julian Foad <julianf...@apache.org> wrote:
Currently: "svn checkout --compatible-version=1.15". No feature name involved. Not saying that's good, just that's the current state.

Are you saying this is how you would activate this no-pristines
feature? If so, that sounds like a poor UX. As a user, I would not expect the version number to be connected to a feature like that Or more accurately, I could understand if you need a 1.15 working copy to enable a WC format that tracks whether or not pristines are available but I would not expect the version number alone to be the factor that
makes this decision. Does that make sense?

FWIW, I just assumed that this *isn't* the intended entry point to the feature. That is, it's just how things happen to be on the branch right now, but (presumably) Julian isn't saying that he thinks this is how users should access the feature in real life.

I have not followed every email on this topic but feel like I have lost understanding of what the feature will do. I thought the original goal was "I have a lot of large binaries, I would like to have a WC
with no pristines in it"

AFAIU, that's the "MVP" goal here, yup.

Assuming I have a WC with large binaries:

* I am not going to use diff
* If I commit a change, I would like to just send the new file to the
server and let it figure it all out
* If I revert, yeah I will need a new copy sent to me
* If I update, and do not have local mods, I will just get a new copy
of file that replaces what I have

* If I update, and have local mods ... less sure what should happen. Is this the scenario where you create a pristine? If it is not a file
where we can do a text merge, then I guess I would just want my
version of the file to remain and ideally not even get the new file
sent to me. If I change my mind, I will do a revert.

Personally, I think a toggle for the whole WC would be fine. And even if I have text files too, the handful of operations like diff where it downloads a pristine to do the diff might be fine as long as it works.
Performance might even be fine.

It sounds like this is not how it works?

I'm not sure that the "fetch base from server if necessary" behavior is part of the MVP (it might be, I'm just not sure -- there are decent workarounds if it's not, after all).

Best regards,
-Karl

Reply via email to