Metadata revisions for elocrypt-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 (elocrypt-0.3.1-r1) 2015-05-18T00:02:37Z sgillespie d5781bd7efe030d5ee31448a6df16a3a6c3e4e72e4cabb73a42ad243240f7f6a
  • Changed source-repository from

    source-repository this
        type:     git
        location: https://github.com/sgillespie/elocrypt.git
        tag:      v0.3.0
    
    to
    source-repository this
        type:     git
        location: https://github.com/sgillespie/elocrypt.git
        tag:      v0.3.1
    

-r0 (elocrypt-0.3.1-r0) 2015-05-15T14:25:56Z sgillespie ec56443d5a6348a2a3d5621bf7554889baf7d1b23f1c2b6dfb527bb11eed776e