RE: 1.9 issues

2014-01-24 Thread Bert Huijben
> -Original Message- > From: Ben Reser [mailto:b...@reser.org] > Sent: vrijdag 24 januari 2014 18:21 > To: Subversion Development > Subject: 1.9 issues > > As we approach a 1.9 release (not sure what our time frame for release is but > I > think we were expecting roughly a year in Berlin

RE: 1.9 issues

2014-01-24 Thread Bert Huijben
I’m not sure if I can call this ‘mtcc library’ / ‘mtcc feature set’ a layering violation. It uses both libsvn_client and libsvn_wc in its implementation, which no other existing libraries currently uses. And in many discussions the result is that we should have never introduced libsvn_wc a

Re: 1.9 issues

2014-01-24 Thread Branko Čibej
On 24.01.2014 18:20, Ben Reser wrote: > 2) libsvn_client_mtcc_*: Should these exist at all or be moved to another > library? This conversation died out. I asked for this API to be marked experimental, and was ignored. I'm not at all happy about that. I'm going to take this opportunity to say -1

Re: 1.9 issues

2014-01-24 Thread Ben Reser
On 1/24/14, 9:49 AM, Stefan Sperling wrote: > My intention is to move into 'svn'. I have started this already but > got side-tracked and didn't get to finish it. I'll try to pick this up. Thanks. > That's because of my fix for issue #4426 (r1524145). I'd be fine > with reverting that change if no

Re: 1.9 issues

2014-01-24 Thread Stefan Sperling
On Fri, Jan 24, 2014 at 09:20:35AM -0800, Ben Reser wrote: > As we approach a 1.9 release (not sure what our time frame for release is but > I > think we were expecting roughly a year in Berlin last year) I think there are > several issues that need to be discussed and final decisions made. I don

1.9 issues

2014-01-24 Thread Ben Reser
As we approach a 1.9 release (not sure what our time frame for release is but I think we were expecting roughly a year in Berlin last year) I think there are several issues that need to be discussed and final decisions made. I don't see any of this as a blocker to 1.9.0-alpha1, but they also provi

Re: "svn diff -r N file" in 1.7.14 is broken if svn:mime-type is present

2014-01-24 Thread Ben Reser
On 1/24/14, 7:52 AM, James McCoy wrote: > > On Jan 4, 2014 5:10 PM, "Ben Reser" mailto:b...@reser.org>> > wrote: >> What's really going on here for anyone that cares about the details is the >> major rework of diff code we added for issues #4153 and #4421 incorrectly >> assumes that the value of

Re: "svn diff -r N file" in 1.7.14 is broken if svn:mime-type is present

2014-01-24 Thread James McCoy
On Jan 4, 2014 5:10 PM, "Ben Reser" wrote: > What's really going on here for anyone that cares about the details is the > major rework of diff code we added for issues #4153 and #4421 incorrectly > assumes that the value of the property in the property hash is a C string when > in fact it is a svn

Re: possible optimization on update at externals with fixed-revision number?

2014-01-24 Thread Johan Corveleyn
On Fri, Jan 24, 2014 at 2:22 PM, Branko Čibej wrote: > On 24.01.2014 14:09, Stefan Sperling wrote: > > On Thu, Jan 23, 2014 at 01:11:36PM +, Kuno Meyer wrote: > > Hi all, > > One of the repositories I am working with has a long list of "svn:external" > links. This has a major impact on working

Re: possible optimization on update at externals with fixed-revision number?

2014-01-24 Thread Branko Čibej
On 24.01.2014 14:09, Stefan Sperling wrote: > On Thu, Jan 23, 2014 at 01:11:36PM +, Kuno Meyer wrote: >> Hi all, >> >> One of the repositories I am working with has a long list of "svn:external" >> links. This has a major impact on working copy update performance, since >> each external link ne

Re: possible optimization on update at externals with fixed-revision number?

2014-01-24 Thread Stefan Sperling
On Thu, Jan 23, 2014 at 01:11:36PM +, Kuno Meyer wrote: > Hi all, > > One of the repositories I am working with has a long list of "svn:external" > links. This has a major impact on working copy update performance, since > each external link needs an additional roundtrip to the (painfully slow