Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Evgeny Kotkov
Evgeny Kotkov writes: > The current state is that the commit is going to fetch the original > text-base before sending the delta. > > It should be technically possible to implement a behavior where the commit > sends a delta if the local text-base is present, and a fulltext otherwise. This behav

Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Evgeny Kotkov
Mark Phippard writes: > > (Although as far as I can tell, we would have to extend the delta editor > > to allow us to send a fulltext against an existing file, and the > > optimization would only work for newer servers.) > > This is just from memory of a list conversation that probably happened

Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Stefan Sperling
On Fri, Aug 27, 2021 at 06:42:34PM +0300, Evgeny Kotkov wrote: > Mark Phippard writes: > > > Suppose I am using this feature for binaries, which I think is the > > main use case. Using whatever tool I produce a modified version of my > > binary file. At this point in time, there is nothing in the

Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Mark Phippard
On Fri, Aug 27, 2021 at 11:42 AM Evgeny Kotkov wrote: > > Mark Phippard writes: > > > Suppose I am using this feature for binaries, which I think is the > > main use case. Using whatever tool I produce a modified version of my > > binary file. At this point in time, there is nothing in the text-b

Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Evgeny Kotkov
Mark Phippard writes: > Suppose I am using this feature for binaries, which I think is the > main use case. Using whatever tool I produce a modified version of my > binary file. At this point in time, there is nothing in the text-base > because I have not done any SVN operations other than checko

Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Mark Phippard
On Fri, Aug 27, 2021 at 9:56 AM Evgeny Kotkov wrote: > > Karl Fogel writes: > > > 1) Make pristine text-base files optional. See issue #525 for > > details. In summary: currently, every large file uses twice the > > storage on the client side, and yet for most of these files > > there's little

Re: A two-part vision for Subversion and large binary objects.

2021-08-27 Thread Evgeny Kotkov
Karl Fogel writes: > 1) Make pristine text-base files optional. See issue #525 for > details. In summary: currently, every large file uses twice the > storage on the client side, and yet for most of these files > there's little benefit. They're usually not plaintext, so 'svn > diff' against th

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Nathan Hartman
On Fri, Aug 27, 2021 at 9:26 AM Johan Corveleyn wrote: > > On Fri, Aug 27, 2021 at 2:03 PM Daniel Shahaf wrote: > > > > Consensus can only result from an open discussion. That's a standard > > ASF operating principle. > > > > The rhetoric in this thread effects chill on anyone who has an opinion

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Johan Corveleyn
On Fri, Aug 27, 2021 at 2:03 PM Daniel Shahaf wrote: > > Consensus can only result from an open discussion. That's a standard > ASF operating principle. > > The rhetoric in this thread effects chill on anyone who has an opinion > different from the opinion of certain speakers. I must say I have

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Stefan Sperling
On Fri, Aug 27, 2021 at 12:02:58PM +, Daniel Shahaf wrote: > Consensus can only result from an open discussion. That's a standard > ASF operating principle. > > The rhetoric in this thread effects chill on anyone who has an opinion > different from the opinion of certain speakers. Could you

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Daniel Shahaf
Consensus can only result from an open discussion. That's a standard ASF operating principle. The rhetoric in this thread effects chill on anyone who has an opinion different from the opinion of certain speakers. Therefore, this thread _cannot_ consense at this time. I think we should (US)table

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Stefan Sperling
On Fri, Aug 27, 2021 at 11:38:57AM +, Daniel Shahaf wrote: > The solution to "credentials can't be used to commit with" is not > *necessarily* "cache a password for a different username". It could > also be that the authz file has a business logic error («r» rather than > «rw»), or that the se

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Daniel Shahaf
Johan Corveleyn wrote on Thu, Aug 26, 2021 at 17:26:50 +0200: > I.e. shouldn't the more general problem statement be "Replace cached > username+passwords that can't be used to commit with"? +1 > (hence my first response with "huh, shouldn't a --username make that > problem moot"? I.e. the user kn

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Daniel Sahlberg
Den fre 27 aug. 2021 kl 09:15 skrev Johan Corveleyn : > On Thu, Aug 26, 2021 at 3:44 PM Mark Phippard wrote: > > > > On Thu, Aug 26, 2021 at 6:30 AM Stefan Sperling wrote: > > > > > The answer might be that 'svn authz add' should simply not contact the > > > server to check credentials. Which me

Re: A strong WTF on compiling out plaintext password support by default?!

2021-08-27 Thread Johan Corveleyn
On Thu, Aug 26, 2021 at 3:44 PM Mark Phippard wrote: > > On Thu, Aug 26, 2021 at 6:30 AM Stefan Sperling wrote: > > > The answer might be that 'svn authz add' should simply not contact the > > server to check credentials. Which means we cannot check upfront whether > > the user running 'svn auth