On 05/23/2013 11:24 AM, Bradley Lowekamp wrote: > Brad, > > Your instructions are great! I am I finding the easy to follow except that > little issue. Please pardon my force push to github.
The content of the new commit looks good. I usually use the date printed out by the extraction script as the --date value on the "git commit" line so that the authorship recorded for the commit not only reflects the upstream developers but the upstream time of the version as well. > The only thing missing is that to initially copy the upstream branch ( when > you are starting something new or a like my case ) into ITK I have used the > following command (after a commit to delete the old): > > git read-tree --prefix=Modules/ThirdParty/OpenJPEG/src/openjpeg -u > openjpeg-upstream That's correct. The VNL instructions leave that out because they are for updating the already-initialized tree. You'll also have trouble pushing/merging it the first time to master but just put the full topic somewhere I can fetch and I'll push it for you. The reason is that there is a server-side hook that blocks new root commits from entering history. It is there to prevent someone from accidentally merging an unrelated project's history into ITK. -Brad K _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Kitware offers ITK Training Courses, for more information visit: http://kitware.com/products/protraining.php Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ Follow this link to subscribe/unsubscribe: http://www.itk.org/mailman/listinfo/insight-developers
