work with "--accept failure" is if svn update also
had --dry-run.
Thanks for your considering this feature.
Marc Pawlowsky
a shared file system. It is a common error to
accidentally perform manual operations on a host that has the wrong svn
version. Especially since the old versions have to be retained on some
workstations.
Thanks for the quick response
Marc
On Dec 2, 2016 12:13 PM, "Daniel Shahaf" wrot
There is a lot of effort and hacks on determining what SVN database
version is being used on the working copy. Usually resorting to
examining the internal contents of a .svn/* file.
For future releases it would be nice if there was a command to display
if the current working copy is at the same l
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
