Metadata revisions for strict-concurrency-0.2.4.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
-r2 (strict-concurrency-0.2.4.1-r2) 2015-11-11T11:19:26Z AdamBergmark 70e871fd6fd7dffa2dc373fda3a062e9b9efde6cbab873b250ff5731ca1a7850
-r1 (strict-concurrency-0.2.4.1-r1) 2015-08-04T00:16:43Z AdamBergmark e9b8d4599f2eae037bb3b6008284513dbb50af7d3ab42e617b76577bdea656a1
-r0 (strict-concurrency-0.2.4.1-r0) 2010-08-12T00:01:30Z DonaldStewart 9607b7ee51bed021446c8cfaa47c3bafbc8cca224a82bf51b55070ba77daba9b