You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jack Bates <ms...@freezone.co.uk> on 2009/03/13 18:37:48 UTC
why merge explicit revisions from path to same path requires
--ignore-ancestry?
In r1214 I merged some changes and accidentally dropped changes which
were committed after March 2nd and before r1214. I can display these
changes by typing this command, in a working copy:
$ svn diff -r {2009-03-02}:1213
I expected I could resurrect these changes with this command:
$ svn merge -r {2009-03-02}:1213 .
- instead, however, it simply exited with no output and no changes : (
danielsh on #svn suggested --ignore-ancestry, and sure enough, this
command merged the changes in the way I intended:
$ svn merge -r {2009-03-02}:1213 . --ignore-ancestry
Now I am trying to understand why --ignore-ancestry was required? I have
reviewed the sections of svnbook on merge and ancestry:
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.branchmerge.advanced.ancestry
- but have not found an explanation why my original merge command did
not merge the changes as I expected?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1318197
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].