David<div><br></div><div>I've been spending some time looking at your Wrapping work. It appears that your git tree was built with a mixture of rebasing and merging which resulted in a somewhat wonky commit history (duplicated commits interspersed with commits coming from VTK master).</div>
<div><br></div><div>In order to get a clean topic branch that will be a little easier for folks here to look at (and to eventually merge with master) I spent a bit of time untangling your history (mostly by examining parentage and looking at commit subjects). In the end, by cherry picking the right commits in what I considered the "right" order I was able to build a clean topic branch with no conflicts. Once I had that, I rebased it against master (as of this afternoon sometime when I did it). The result can be found in </div>
<div><br></div><div>git://<a href="http://github.com/keith-fieldhouse/VTK.git">github.com/keith-fieldhouse/VTK.git</a></div><div><br></div><div>As the topic branch Gobbi/Wrapping.</div><div><br></div><div>The result builds and the tests run so I believe that I've built a a representative branch from your work.</div>
<div><br></div><div>If you plan on doing additional work on this, would it be possible for you to grab this topic branch and work on that (without rebasing or merging for now)? That way we'll have a clean topic branch for an eventual merge to "Next" when we switch to branchy development for VTK. Or if branchy development comes later, this clean topic branch will be easier to rebase as well.</div>
<div><br></div><div>Thanks again for your work on this.</div><div><br></div><div>Keith </div><div><br></div><div>--</div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">Keith Fieldhouse<br>
R&D Engineer, Kitware Inc.<br>(518) 836-2190</span></div><div><br></div><div><br></div><div><br></div><div><br></div>