If it is possible to include and would not be a big pain to do, then I do agree that it should be included. TrueCrypt's history is CipherShed's history, so I do think it belongs, and could be useful, for the reasons you stated. Alain -----Original Message----- From: ciphershed-bounce@xxxxxxxxxxxxx [mailto:ciphershed-bounce@xxxxxxxxxxxxx] On Behalf Of Dimitri Schoolwerth Sent: Tuesday, June 17, 2014 14:42 To: ciphershed@xxxxxxxxxxxxx Subject: [ciphershed] TrueCrypt development history Hi, Is there (still) interest in having the development history of TrueCrypt in the repository? The diff granularity will obviously be at the level of TrueCrypt releases rather than per change (although most of the early release actually do document the CVS changes in Changelog.txt). But I think that's still a very valuable resource when (rather than if) for example git blame is used. Having the history in another repository is an option but it would rather defeat the purpose, having to check another repository. An example of the repository is available at: https://github.com/discnl/truecrypt-source-archive Created using the bash conversion script at: https://github.com/discnl/convert-truecrypt-archives Using the tar.gz and zip source archives from: https://github.com/DrWhax/truecrypt-archive Regards, Dimitri