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 bryce . schober
options to switch, merge, etc. I suppose directions like that may have been taken before with svn wrapper systems, but those never catch on or survive unless they are upstream. <>< <>< <>< Bryce Schober On Tue, Aug 27, 2019 at 2:43 AM Johan Corveleyn wrote: > On

Remote renames create subtree mergeinfo

2019-08-21 Thread Bryce Schober
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?