nicholas a. evans

@zenspider Thanks for the feedback. The v0.4.0 release was a big one, but I did try to keep incompatibility to a minimum. In some cases incompatibilities were accidental or bugs,...

I took a quick look through the release notes and added the following breaking change to [the v0.4.0 release notes](https://github.com/ruby/net-imap/releases/tag/v0.4.0): > * The `#extension` attribute on BODYSTRUCTURE structs no longer...

> Known cheeky response, but I think when your 0.x is literally 2 decades old, you're not really allowed to be considered "unstable" at that point, no? Well, there _is_...

My forked client has been using this for years. It is incredible how much it reduces bandwidth consumption. The last time I attempted to implement it in `Net::IMAP`, I ran...

@mperham instead of locking to mail 2.7.1, you could lock the `date` gem to ```ruby Gem::Specification.find{_1.name == "date" && _1.default_gem?}.version ``` You could even add that to the Gemfile (although...

@mperham, I was about to start a discussion over at https://github.com/rubygems/rubygems, but then I wondered if the feature I wanted wasn't already supported. So I read through the bundler docs...

> I think explicitly locking versions with a comment is superior to using Bundler in a non-default mode. The KISS principle. 99% of Ruby developers, including myself, have no idea...

n.b: `ExtensionData` was added as part of #225. I still think it could be nice to have special hash/array/string/numeric versions (as in #127, #128, #129)

cc: @stanhu Because of #24 and also your comments on https://github.com/ruby/digest/issues/14, I assume you're experiencing this issue too?

yeah, I saw that too. And it's even marked for backport to 2.5! Unfortunately, it's not available today. Do you know of a workaround other than installing the gem as...