Re: svn commit: r1730389 - /subversion/trunk/subversion/libsvn_repos/log.c

On 15.02.2016 09:39, Ivan Zhakov wrote: On 14 February 2016 at 22:25, wrote: Author: stefan2 Date: Sun Feb 14 19:25:12 2016 New Revision: 1730389 URL: http://svn.apache.org/viewvc?rev=1730389=rev Log: Begin work on the svn_repos_get_logs4 to svn_repos_get_logs5 migration.

RE: svn commit: r1730617 -/subversion/trunk/subversion/libsvn_repos/log.c

Are you sure the pool arguments are in the right order here? The usual order is result_pool, scratch_pool while most of the calls here appear to use the opposite order. Bert Sent from Mail for Windows 10 From: stef...@apache.org Sent: maandag 15 februari 2016 22:47 To:

RE: svn commit: r1730546 - in /subversion/trunk/subversion:include/private/svn_wc_private.h libsvn_client/resolved.clibsvn_wc/conflicts.c

There shouldn’t be many cases where the wait is necessary, if any… Resolving a conflict never involves changing BASE and typically we already waited before invoking the resolver. So this could be as simple as just removing the waits. (I can’t really think of a case in tree/property conflicts

Re: Merging parallel-put to /trunk

> I think that local commits are usually fast enough. But committing over > a high-latency network, e.g., with a transatlantic RTT of 150ms, can be > painfully slow — see below. Poor network connections are of course a very important concern, likely even more important than some additional

Re: svn commit: r1730546 - in /subversion/trunk/subversion: include/private/svn_wc_private.h libsvn_client/resolved.c libsvn_wc/conflicts.c

On Mon, Feb 15, 2016 at 05:30:55PM +0100, Bert Huijben wrote: > Why would you need to wait for timestamps here? > > Can this change the working copy file? > > If it can the wc function should probably return a boolean to notify the case > where it does, and only when it does we should wait for

RE: svn commit: r1730546 - in /subversion/trunk/subversion: include/private/svn_wc_private.h libsvn_client/resolved.c libsvn_wc/conflicts.c

See inline. > -Original Message- > From: s...@apache.org [mailto:s...@apache.org] > Sent: maandag 15 februari 2016 16:04 > To: comm...@subversion.apache.org > Subject: svn commit: r1730546 - in /subversion/trunk/subversion: > include/private/svn_wc_private.h libsvn_client/resolved.c >

Re: SVN::Client::log() first argument Re: svn commit: r1729519 - /subversion/trunk/tools/client-side/svn-graph.pl

On Mon, Feb 15, 2016 at 11:54:39AM +0100, Bert Huijben wrote: > > -Original Message- > > From: James McCoy [mailto:vega.ja...@gmail.com] On Behalf Of James > > McCoy > > Sent: zondag 14 februari 2016 19:20 > > To: Daniel Shahaf > > Cc: dev@subversion.apache.org >

RE: SVN::Client::log() first argument Re: svn commit: r1729519 - /subversion/trunk/tools/client-side/svn-graph.pl

> -Original Message- > From: James McCoy [mailto:vega.ja...@gmail.com] On Behalf Of James > McCoy > Sent: zondag 14 februari 2016 19:20 > To: Daniel Shahaf > Cc: dev@subversion.apache.org > Subject: Re: SVN::Client::log() first argument Re: svn commit: r1729519

Re: What's an svnserve groups-db file? Fwd: [C. Michael Pilato: Re: [svnbook] r5084 committed - trunk/en/book/ch06-server-configuration.xml]

Daniel Shahaf writes: > From the default svnserve.conf: > > ### The groups-db option controls the location of the groups file. > ### Unless you specify a path starting with a /, the file's location is > ### relative to the directory containing this file. The

Re: svn commit: r1730389 - /subversion/trunk/subversion/libsvn_repos/log.c

On 14 February 2016 at 22:25, wrote: > Author: stefan2 > Date: Sun Feb 14 19:25:12 2016 > New Revision: 1730389 > > URL: http://svn.apache.org/viewvc?rev=1730389=rev > Log: > Begin work on the svn_repos_get_logs4 to svn_repos_get_logs5 migration. > > As a first step, we