version control - svn local obstruction, incoming add upon merge -


i have read quite few threads on , following blogg still don't understand particular issue hope can help...

doing merge mainline dev line catch again , following tree conflict.

m      incubator      c incubator/utilityscripts      >   local dir obstruction, incoming dir add upon merge 

okay, understand should directory independently added both trunk , dev branch independently such there no common ancestor...

..buuuut (there's right?!) there common ancestor. directory entered dev branch because of previous merge truck.

dev$ svn mergeinfo {^/trunk/src/,}incubator/utilityscripts/      youngest common ancestor      |         last full merge      |         |        tip of branch      |         |        |         repository path       23788              23838         |                  |           -------| |------------         trunk/src/incubator/utilityscripts       \                                 \                                --| |------------          branches/dev/src/incubator/utilityscripts                          |                                23838    

so, understand svn believe dev branch ancestrally related trunk common ancestor @ revision 23788.

branch$ svn log --stop-on-copy incubator/utilityscripts/ ------------------------------------------------------------------------ r23790 | me | 2015-05-12 16:08:25 +0100 (tue, 12 may 2015) | 1 line 

so got file in revision 23790 , @ revision 23838

trunk$ svn log --stop-on-copy incubator/utilityscripts/ ------------------------------------------------------------------------ r23639 | | 2015-03-06 10:59:10 +0000 (fri, 06 mar 2015) | 1 line 

so, common ancestor 23788. revision @ entered dev branch 23790 after anyway.the recent trunk change 23639 before of these.

so given this, how on earth can there incoming add conflict?!


Comments

Popular posts from this blog

Email notification in google apps script -

c++ - Difference between pre and post decrement in recursive function argument -

javascript - IE11 incompatibility with jQuery's 'readonly'? -