why merge explicit revisions from path to same path requires --ignore-ancestry?
From: Jack Bates <ms419_at_freezone.co.uk>
Date: Fri, 13 Mar 2009 11:37:48 -0700
In r1214 I merged some changes and accidentally dropped changes which
$ 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
$ svn merge -r {2009-03-02}:1213 . --ignore-ancestry
Now I am trying to understand why --ignore-ancestry was required? I have
- but have not found an explanation why my original merge command did
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.