Metadata revisions for crypto-api-0.3.1

Package maintainers and Hackage trustees are allowed to edit certain bits of package metadata after a release, without uploading a new tarball. Note that the tarball itself is never changed, just the metadata that is stored separately. For more information about metadata revisions, please refer to the Hackage Metadata Revisions FAQ.

No. Time User SHA256
-r1 (crypto-api-0.3.1-r1) 2019-01-23T09:16:41Z HerbertValerioRiedel 02e37c5c5dd24da7f241519de1486143d83106c656887b159d89fcf9386ae844
-r0 (crypto-api-0.3.1-r0) 2011-01-07T07:14:27Z ThomasDuBuisson 821dcb3c4d9edfe56c91533962bdd129b7cd4517919169bf434d7fa8967ad204