Note that the commit logic in libsvn_client uses exactly the same driver
pattern, but even in a more extreme way: it opens all nodes before closing the
first file that will receive content changes.
Serf was only the first driver to do it this way in the other direction.
Bert
Sent from
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from git svn fetch:
Temp file with moniker 'svn_delta' already in use at
/usr/lib/perl5/vendor_perl/5.10/Git.pm line 1024.
This occurs only when using an http:// URL; svn:// URLs work fine.
I think this
On 05.07.2013 19:15, David Rothenberger wrote:
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from git svn fetch:
Talk to the authors of git-svn. This is a Subversion users' mailing list.
--
Branko Čibej | Director of Subversion
WANdisco //
On 7/5/2013 10:49 AM, Branko Čibej wrote:
On 05.07.2013 19:15, David Rothenberger wrote:
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from git svn fetch:
Talk to the authors of git-svn. This is a Subversion users' mailing list.
Thanks, but I'm
On 05.07.2013 21:07, David Rothenberger wrote:
On 7/5/2013 10:49 AM, Branko Čibej wrote:
On 05.07.2013 19:15, David Rothenberger wrote:
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from git svn fetch:
Talk to the authors of git-svn. This is a
On 7/5/2013 2:10 PM, Branko Čibej wrote:
On 05.07.2013 21:07, David Rothenberger wrote:
On 7/5/2013 10:49 AM, Branko Čibej wrote:
On 05.07.2013 19:15, David Rothenberger wrote:
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from git svn fetch:
On 7/5/2013 3:58 PM, Kyle McKay wrote:
On Jul 5, 2013, at 13:48, David Rothenberger wrote:
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from git svn fetch:
Temp file with moniker 'svn_delta' already in use at
[Copying dev@ because it's related to a known issue that we document
more loudly.]
On 06.07.2013 00:51, David Rothenberger wrote:
I cannot reproduce this problem using command-line tools, but I was
able to do a trace of git-svn when it is failing and it looks to me
that the problem is in the
On 06.07.2013 02:34, Branko Čibej wrote:
In the meantime, it might be a good idea to relax the restrictions in
git-svn to account for the way the HTTPv2 protocol works.
By the way, this section of the 1.8 release notes is relevant:
