On Thu, 22 Dec 2016 13:48:47 +, Stefan Sperling wrote:
...
> I think this idea is short-sighted. I can imagine this suggestion to cause
> major inconvenience if implemented.
I know of a VCS having done exactly this.
> Inevitably, an environment variable will point to a .svn directory of one
>
On 12/21/2016 10:53 AM, Daniel Shahaf wrote:
If it had become obsolete it wouldn't have been removed from the
mailer.py code to maintain backwards compatibility. More likely, that
parameter never existed in mailer.py as distributed by us. The comment
in that blog suggests it's a local patch by
On Tue, Dec 20, 2016 at 9:30 AM, Matt Garman wrote:
> On Tue, Dec 20, 2016 at 1:49 AM, Nico Kadel-Garcia wrote:
>> On Mon, Dec 19, 2016 at 6:10 PM, Matt Garman
>> wrote:
>>> Looking at the Subversion 1.7 release notes[2], and also my own
>>> testing, it appears that what I could do to make this
On Thu, Dec 22, 2016 at 01:52:01PM +0100, Olaf van der Spek wrote:
> On Thu, Dec 22, 2016 at 1:48 PM, Stefan Sperling wrote:
> > I think the use case described would be much better served by implementing
> > support for a shared .svn dir located e.g. in the user's home directory
> > which
> > can
On Thu, Dec 22, 2016 at 1:48 PM, Stefan Sperling wrote:
> I think the use case described would be much better served by implementing
> support for a shared .svn dir located e.g. in the user's home directory which
> can then be shared by multiple working copies.
> This would work without an env va
On Thu, Dec 22, 2016 at 11:47:41AM +, Daniel Shahaf wrote:
> Allowing to specify the location fo the .svn dir through a --option or
> envvar does not require sharing .svn dirs amongst different working
> copies.
>
> The only code change that should be needed is a short-circuit codepath
> in th
Branko Čibej wrote on Thu, Dec 22, 2016 at 11:03:27 +0100:
> On 21.12.2016 17:57, Miller, Hugh wrote:
> >> What is the problem you are trying to solve?
> > The context is versioning file sets/trees that are used by other
> > applications and processes. In this situation, it is nice or imperative t
On 21.12.2016 17:57, Miller, Hugh wrote:
>> What is the problem you are trying to solve?
> The context is versioning file sets/trees that are used by other applications
> and processes. In this situation, it is nice or imperative to be able to
> treat the file set/tree as just the original, but s
Hi,
I am suprised by poor performance of svnserve and not sure how can I improve
it.
Test case
I am on a Windows 10 laptop with i7 and SSD. (tested on Windows server too
with similar performance)
I am running both server and client on the laptop - so it doesn't go through
the network.
