Guten Tag Marc Pawlowsky,
am Samstag, 29. März 2014 um 19:22 schrieben Sie:
> Can someone please confirm that svn 1.8.8 cannot work on the files
> that were checked out with the older version.
It's documented in the release notes:
> Subversion 1.8, however, requires an upgrade for both read and
Hello,
After setting up SVN protocol (using svnserve windows process) I get this kind
of error when perform commit.
Regards,
Omer Abramovich
IS/ITDepartment
Mobile 052.8588.111
[Syverse Logo]
<>
svn-crash-log20140327204608.log
Description: svn-crash-log2014032720
I am on two different hosts with different SVN versions.
Host1 is using svn client 1.6.18 and checks out all the files.
Host2 is using svn client 1.8.8 and using NFS works on the same files as
Host1. e.g. The actual files are shared across machines, not copies.
I cannot upgrade the files with sv
Hi, and thanks in advance for your assistance. I'm a newbie. But, I'm
learning
I'm preparing to "make install" Subversion 1.8.8 on a centos 5.9 box using the
following prerequisites:
Apr-Util-1.5.3
SQLite-3.8.4.1
OpenSSL-1.0.1f
Serf-1.3.4
Python 2.7.6 (also have the default Python 2.4 ins
On Sun, Mar 30, 2014 at 8:51 PM, Ryan Schmidt
wrote:
> I've been developing a new feature of a public project in secret, in my own
> private Subversion repository. It's almost entirely new code in a new
> directory. There's only one file that's based on an existing file, and it's
> been heavily
I’ve been developing a new feature of a public project in secret, in my own
private Subversion repository. It’s almost entirely new code in a new
directory. There’s only one file that’s based on an existing file, and it’s
been heavily rewritten.
There will come a time when I will want to publis
