Eric, > Oh... Any chance that lost commit you couldn't find was clobbered > by filter-branch? That would explain a lot... I still have the AWS repo as it was from initial import. And I can see the commit on this one: $ git log --all --parents | grep d2cf08bb67e4b7da33a250127aab784f1f2f58d3 commit bd95b2b254286e6f04015b7f58266d66abc134a7 d2cf08bb67e4b7da33a250127aab784f1f2f58d3 commit d2cf08bb67e4b7da33a250127aab784f1f2f58d3 406eaf7e51229f60048ea80cdb6904e33ef59a81 So that's definitely a problem with the filter-branch. Thanks a lot for your precious help! Will review the procedure for filtering branches :( Pascal. -- --|------------------------------------------------------ --| Pascal Obry Team-Ada Member --| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE --|------------------------------------------------------ --| http://www.obry.net --| "The best way to travel is by means of imagination" --| --| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html