endgame

No, I tried to preview a change like that, and Hackage only allows revisions which change dependency information.

With #875, there is very little need for Amazonka to care about a specific `Logger` type, and it could be deprecated and removed. Some downstream libraries (example: @axman6 's [`amazonka-s3-streaming`](https://github.com/axman6/amazonka-s3-streaming))...

That would mean the generator would have to compile in its overrides and other config, which wouldn't be great for making it useful in other contexts. For a while, Amazon's...

#875 calls `logDebug` on all failures and `logError` on the final failure.

Someone put it back into stackage, it seems. Closing.

Thank you for that. Re: V2s: I think that's `botocore`'s fault. If you look at https://github.com/boto/botocore/tree/develop/botocore/data you will see a similar pattern. Trying to smooth over irregularities across the entire...

I'm going to close this off. `connection` is up to `0.3.1`; `tls` is up to `2.0.2` on Hackage and `1.8.0` on nixpkgs `master`. I don't think anyone will need/want/be able...

https://github.com/commercialhaskell/stack/pull/6343 has been merged.

Looks like it went to Hackage as part of the 2.0 release. Whether it goes into stackage is stackage's business.

About five months ago, a botocore update added HTTP status codes to the S3 service definition: https://github.com/boto/botocore/blob/c5ddcdbe0d53d1a7027ddfa94de40ae7646bec7e/botocore/data/s3/2006-03-01/service-2.json#L7466 I advanced the `botocore` pin, regenerated the S3 SDK, and tested it thus:...