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: 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?

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?

Re: Subtree mergeinfo

2012-09-19 Thread Michael T
ous mergeinfo > > modifications during merges. See here for more information: > > http://subversion.apache.org/docs/release-notes/1.7.html#subtree- > > mergeinfo-recording [...] > > Good advice. Get users on 1.7 clients! For the cases where a sub-tree was merged, a relative

Re: Subtree mergeinfo

2012-09-19 Thread Stefan Sperling
d-bean.com/en/1.7/svn.branchmerge.advanced.html#svn.branchmerge.advanced.blockchanges So it all depends on what you really want the mergeinfo to say. If you don't know what you want it to say and how to get there, I'd recommend to rely on Subversion to figure it out. After all, it knows how to

RE: Subtree mergeinfo

2012-09-19 Thread
> -Original Message- > From: Stefan Sperling [mailto:s...@elego.de] > Sent: Wednesday, September 19, 2012 6:26 AM > To: Michael T > Cc: users@subversion.apache.org > Subject: Re: Subtree mergeinfo > > On Wed, Sep 19, 2012 at 01:12:50PM +, Michael T wrote: >

RE: Subtree mergeinfo

2012-09-19 Thread Michael T
not be asking your question in the first place :) > > The easiest thing to do is to just leave the mergeinfo alone > and upgrade all clients to 1.7. This will get rid of superfluous > mergeinfo modifications during merges. See here for more information: > http://subversion.apache.org/d

Re: Subtree mergeinfo

2012-09-19 Thread Stefan Sperling
acking calculations work (in which case you probably would not be asking your question in the first place :) The easiest thing to do is to just leave the mergeinfo alone and upgrade all clients to 1.7. This will get rid of superfluous mergeinfo modifications during merges. See here for more infor

Subtree mergeinfo

2012-09-19 Thread Michael T
Hello, I am aware that this is a much asked question, but since I have nonetheless been unable to find an answer which quite works for me I will ask it again. Feel free to point me to a FAQ I have missed by way of answer if appropriate! We have a large project with multiple branches versioned wi