Merge where a target is missing - skip or tree conflict?
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Tue, 25 Mar 2008 19:03:43 +0000
Currently, "svn merge" can print
Skipped 'foo'
or
Skipped missing target 'foo'
in some situations, and mark the corresponding file or directory "foo" as not
The setting of explicit mergeinfo in this situation was addressed by Issue
This "skipping" strikes me as something we should perhaps convert to a tree
Can anyone think of a situation where it is best for an attempted merge to skip
Situations where this can happen:
* A missing source could be caused by an authorisation restriction. I can't
* A missing target include could be cause by a shallow WC or an
For perhaps the most complex related behaviour, consider a switched sub-tree in
- Julian
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.