Daniel Sahlberg wrote on Tue, Mar 08, 2022 at 14:34:06 +0100: > Den tis 8 mars 2022 kl 14:17 skrev Daniel Shahaf <d...@daniel.shahaf.name>: > > > An alternative is to require the user to let svn know before they're > > starting to edit a file, so we can create a pristine off the on-disk > > file. This way we won't have pristineless modified files in the first > > place. > > > > Not "require". It might be an interesting for some use-case to have "svn > create-pristine-from-wc" as a manual step, but not adding this as part of > the normal workflow. I have some wc's that might benefit from being > pristine-less, but I'm not prepared to pay the extra cost (time-wise) of an > svn:needs-locking-like step for every file I need to modify. I don't think > this new command (or option) is MVP.
I wasn't proposing we require such a step. I was merely saying that was one of several possible solutions to the "How to commit a pristineless file" question. Here they are again: 1. Download the pristine and then send a regular delta 2. Send a self-delta 3. rsync the file 4. Avoid getting into this situation in the first place I guess we'll be happy with (2) for the MVP. Cheers, Daniel
