DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40785>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40785 ------- Additional Comments From [EMAIL PROTECTED] 2006-10-18 03:45 ------- I've traced through the merge process (printing out the structure addresses of each dir make and dir merge operation). It looks like this (starting from top going down, as we move down the parameters passed SHOULD be a higher priority): parent(0x8ee2f58) 'Off' | child(0x8ee7f38) 'Off' | _____| \/ [blank](0x8e65b10) merged(0x8ee4e98) | | __________________| \/ merged(0x8ee51d8) | parent<Files>(0x8ee35c8) | _____| \/ merged(0x8ee5720) As can be seen the merge order makes little logical sense apart from the first merge. Yes, the child should take priority over the parent to create a merged record. But merging that with a blank record? And then merging in the parent <Files> record? No, that's definately not right. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
