Den tis 3 mars 2026 kl 18:32 skrev Sean Palmer <[email protected]>: > Yeah, e.g. if we added a feature for users to import from > any arbitrary 3rd party repository we'd rather set the disk > space budget in the Subversion client itself. For export > that's straightforward. For a checkout, as I understand it > the working copy metadata is always on the same disk and > can be substantial, so we'd definitely want that to be > included in the calculation. I see that --store-pristine=no > is planned for 1.15, so I guess you're already thinking > about disk space. We probably wouldn't base an import > feature on checkout though. Obviously we could impose disk > space limits at other layers, but since the client knows > what it's writing that would be more convenient and more > portable. > > --sbp >
Hi, Thanks for adding more details! Yes, the --store-pristine=no is specifically for large binary files that rarely change just a small piece. Compressed files might be a prime example. Assuming we have a --space-limit=512M argument. I would assume the client should calculate the disk space requirement beforehand and bail out "Unable, would use 768M". Starting the checkout (or export) process and then aborting halfway through wouldn't make much sense. I'm not really sure I see a general use case for this (although I understand it could be a handy feature in your case). Cheers, Daniel
