[ 
https://issues.apache.org/jira/browse/SVN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289478#comment-17289478
 ] 

Daniel Shahaf commented on SVN-525:
-----------------------------------

The one thing I have to add to Karl's excellent reply is that we don't have to 
figure out the user-facing aspects right off the bat; starting with a prototype 
that has _some_ UI, just enough for devs and interested users to try the 
feature out (no compatibility promises), would be reasonable.  E.g., a 
configuration knob that takes a space-separated list of 
repository-root-relative paths could work well enough for prototype purposes.

We even have precedent for releasing features in a "no compatibility promises 
for this specific feature/API" fashion: see, for instance, 
<https://subversion.apache.org/docs/release-notes/1.11.html#cmdline>.

And yes, please introduce yourself on dev@ :-)


> Allow working copies without .svn/pristine/ cache (a.k.a. "text-base/" files).
> ------------------------------------------------------------------------------
>
>                 Key: SVN-525
>                 URL: https://issues.apache.org/jira/browse/SVN-525
>             Project: Subversion
>          Issue Type: New Feature
>    Affects Versions: all
>         Environment: other
>            Reporter: Ben Collins-Sussman
>            Priority: Minor
>             Fix For: unscheduled
>
>
> 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|https://issues.apache.org/jira/browse/SVN-525?focusedCommentId=17256056&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17256056]
>  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.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to