On May 17, 2012 10:38 PM, "Hyrum K Wright" <hyrum.wri...@wandisco.com> wrote: > > Thanks for taking a look. It feels like all of these are issues with > the complex copies and inheriting the correct replacement revision. > The problem then lies back in the commit driver, but I don't think it > will be too hard to track down.
Yeah. I seem to recall the specific code where a revision is tested against its patent. Where those happen, simply use the parent rev for REPLACES_REV. I think that might be in the harvester, where we set the COPY flag. Not sure how that will translate over to the driver, or if it is even applicable. I guess any copy-dest-within-dest needs the parent rev. > The blame test failure is an unrelated EOL repairing issue. Yeah, so I skipped looking into that one. Cheers, -g
