Unexpected HTTP status 405 "Method Not Alloweed" on '/csvn/login/auth"

2019-08-27 Thread Tanner Snedden
192.168.26.207 - cbennett [27/Aug/2019:08:27:22 -0600] "GET / HTTP/1.1" 200 44 0 192.168.26.207 - - [27/Aug/2019:08:27:22 -0600] "OPTIONS / HTTP/1.1" 401 381 0 192.168.26.207 - cbennett [27/Aug/2019:08:27:22 -0600] "OPTIONS / HTTP/1.1" 200 - 0 192.168.26.207 - cbennett [27/Aug/2019:08:27:22 -0600]

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread Nathan Hartman
On Tue, Aug 27, 2019 at 10:24 PM Nathan Hartman wrote: > All of this would happen only if svn:project is set on that directory. If > not, then "svn branch" and "svn tag" are not valid commands and will error > out, while "svn merge" and "svn switch" continue to work as they do today, > namely you

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread Nathan Hartman
On Tue, Aug 27, 2019 at 12:42 PM wrote: > FWIW, I found the explanations in these two emails from the same thread to > be easier to understand as a user: > https://svn.haxx.se/users/archive-2010-11/0408.shtml > https://svn.haxx.se/users/archive-2010-11/0466.shtml > > This sounds like yet another

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread bryce . schober
I disagree: I still use svn because of its centralized nature and good native out-of-the-box handling of large binary files. Git will never really check those boxes. On Tue, Aug 27, 2019, 4:02 PM Nico Kadel-Garcia wrote: > On Tue, Aug 27, 2019 at 12:42 PM wrote: > > > > FWIW, I found the explan

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread Nico Kadel-Garcia
On Tue, Aug 27, 2019 at 12:42 PM wrote: > > FWIW, I found the explanations in these two emails from the same thread to be > easier to understand as a user: > https://svn.haxx.se/users/archive-2010-11/0408.shtml > https://svn.haxx.se/users/archive-2010-11/0466.shtml > > This sounds like yet anothe

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread Daniel Shahaf
bryce.scho...@gmail.com wrote on Tue, Aug 27, 2019 at 09:41:37 -0700: > FWIW, I found the explanations in these two emails from the same thread to > be easier to understand as a user: > https://svn.haxx.se/users/archive-2010-11/0408.shtml > https://svn.haxx.se/users/archive-2010-11/0466.shtml > >

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread Stefan Sperling
On Tue, Aug 27, 2019 at 09:41:37AM -0700, bryce.scho...@gmail.com wrote: > FWIW, I found the explanations in these two emails from the same thread to > be easier to understand as a user: > https://svn.haxx.se/users/archive-2010-11/0408.shtml > https://svn.haxx.se/users/archive-2010-11/0466.shtml >

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread bryce . schober
FWIW, I found the explanations in these two emails from the same thread to be easier to understand as a user: https://svn.haxx.se/users/archive-2010-11/0408.shtml https://svn.haxx.se/users/archive-2010-11/0466.shtml This sounds like yet another UX flaw caused by the constraints of subversion's cha

Re: Questions about a script for regular backups

2019-08-27 Thread Mark Phippard
On Tue, Aug 27, 2019 at 5:06 AM Johan Corveleyn wrote: > On Mon, Aug 26, 2019 at 9:01 PM Mark Phippard wrote: > > > > On Mon, Aug 26, 2019 at 1:29 PM Anton Shepelev > wrote: > >> > >> I have now set up a post-commit hook that makes an > >> --incremental hotcopy. With the destination on the sam

Re: Remote renames create subtree mergeinfo

2019-08-27 Thread Johan Corveleyn
On Wed, Aug 21, 2019 at 6:55 PM Bryce Schober wrote: > > I just noticed that whenever we do a remote rename (from URI to URI, as > opposed to in a working copy), svn add mergeinfo that didn't exist before. It > doesn't do this for renames in a working copy. Is this by design, or by > accident?

Re: Questions about a script for regular backups

2019-08-27 Thread Johan Corveleyn
On Mon, Aug 26, 2019 at 9:01 PM Mark Phippard wrote: > > On Mon, Aug 26, 2019 at 1:29 PM Anton Shepelev wrote: >> >> I have now set up a post-commit hook that makes an >> --incremental hotcopy. With the destination on the same >> machine's HDD, it takes about two seconds, but with a >> network s