> > This has caused significant performance issues especially with svn log.
> > There reasoning was if they could ignore properties this would help combat
> > these performance issues.
> >
> > Does this make sense?
> This sounds as if the performance issue was on the server side.
We found that ab
That would be very useful to be able to show-paths just for the target
and control the depth.
Thanks,
- Mark
-Original Message-
From: Julian Foad [mailto:julianf...@btopenworld.com]
Sent: Friday, August 23, 2013 5:48 AM
To: Ben Reser
Cc: Patrick Sawyer; dev@subversion.apache.org; Support
Would it be possible for the blocked read operations to hang for a
configured "X" number of seconds (maybe with a "waiting X seconds for
exclusive-mode lock to free up" message)?
This would be useful for both (1) waiting just a little bit of time to
prevent unnecessary failure errors and (2) expla
> Now, if we can find a way to expose the revprops to the start-commit hook,
> all three RA layers should be able to provide early detection of commits
> that would fail in pre-commit for revprop-related reasons. (And we should
> consider this independently of the whole client-version capability s
> ALSO: I got a private mail response to my previous post on this thread
> which expressed a good deal of excitement regarding the possibility of
> start-commit having access to the revprops (especially svn:log).
That would be very useful. We have transactions that can be 1GB in
size or more and
This would be useful for our us too. I would add "freeze" to the start and
"unfreeze" to the end of the script we use to rsync a copy of our repo (and
associated files) to an off-site network share.
Thanks,
- Mark
> Can/should we focus on fixing these and shipping sooner rather than
> later? Are there items that should/must go into 1.8 that aren't on
> deck today?
I would really like to see #4176 resolved in v1.7.x or v1.8.x. It's a
major issue for us and our usage of svn (wc-ng) working copies on network
I created Issue #4193. Thanks.
- Mark
On Tue, Jun 12, 2012 at 3:50 PM, Stefan Sperling wrote:
> On Tue, Jun 12, 2012 at 09:50:17AM -0500, Mark Moe wrote:
>> Hi, Subversion 1.7.x appears to no longer support commit (or add) of a
>> file referenced through a symbolic link.
Hi, Subversion 1.7.x appears to no longer support commit (or add) of a
file referenced through a symbolic link. Was this change intended or
should it still work like it did with v1.6.x?
Examples for 1.7.x failing and 1.6.x working shown below.
Thanks,
- Mark
### 1.7.5 ci though link fails ###
This is a big deal for us too. Will there be a configuration setting in an
official svn 1.7.x version that we can use to enable the exclusive lock mode
for SQLite? (assuming that is a valid fix for this issue)
As it is Subversion 1.6 was slow on NFS for us and 1.7 is even worse. But,
our IT de
10 matches
Mail list logo
