Details
-
New Feature
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
all
-
None
-
None
-
other
Description
It's possible to make the cached pristine files in .svn/pristine/ optional. Doing so would be a huge storage savings on the client side, and would make Subversion even more compelling as a system for managing medium-large binary files.
A much more technically thorough explanation of this issue and its background is available in this 2020-12-29 comment below.
(Note that the cached pristine base versions used to be stored in .svn/text-base/, so you'll probably see references to that old location throughout this ticket. Also, there used to be one .svn/ directory per working tree directory; later that was changed to one .svn/ directory at the top of the working tree. Knowing that might also help clarify some of the older comments in this ticket.)
Attachments
Issue Links
- depends upon
-
SVN-3357 Working Copy - Next Generation Library
- Closed
-
SVN-2539 Isolate all textbase access into a single submodule
- Closed
- is blocked by
-
SVN-4891 Pristines-on-demand: fix disabled tests
- In Progress
-
SVN-4889 Pristines-on-demand: per-WC config
- Open
-
SVN-4896 Review crash-safety of new temporary files
- Open
-
SVN-4893 Pristines-on-demand: user guide
- Closed
-
SVN-4898 Pristines-on-demand: make buildbots test it
- Open
-
SVN-3357 Working Copy - Next Generation Library
- Closed
-
SVN-2539 Isolate all textbase access into a single submodule
- Closed
- is duplicated by
-
SVN-2407 RFE: allow "lightweight" working copy.
- Closed
-
SVN-2520 Working copy optimized for space not time
- Closed
-
SVN-2610 Out-of-tree .svn directories
- Closed
- relates to
-
SVN-4888 Pristines-on-demand: authz denied during textbase sync
- Open
-
SVN-4892 Pristines-on-demand: update must not fetch pristines it doesn't need
- Open
-
SVN-4897 Pristines-on-demand: printing progress notifications
- Open
-
SVN-4894 Pristines-on-demand: an explicit "hydrate" command
- Open
-
SVN-4895 Commit without trying to compute a delta
- Open