-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rmail being maintained again #394
Comments
Great! We should definitely move over to your fork and drop sup-rmail |
this is interesting. given that the switch-over to mail has not made much progress, it would be interesting to know what were/are the issues with rmail, and then to evaluate if fixing them is easier than completing the switch-over to mail. |
Great! We should definitely move over to your fork and drop sup-rmail
from rubygems. Do you have all our changes (or equivalent) incorporated
already?
yes, as far as I can tell.
|
On your repository you don't allow for opening issues, and also the web page you refer to leads nowhere. |
ah sorry I didn't notice that I had to explicitly enable issues. Did that just now. re homepage I guess you meant the one in the repo description, that was just copied from the original repo I guess, I deleted that. |
Hi, there has been an open PR on your repository since july (not judging, lots of open here too). I am just wondering whether you are still maintaining your fork, otherwise it is not much point in switching from rmail-sup. |
I am maintaining it. Merging changes to the README is not exactly high on my TODO list though. |
Ok, just switched over to your fork. Seems like all rmail related tests pass on our side. |
I got in touch with the gem owners for rmail and permission to push new versions. I have added a bunch of patches that got accumulated in the Debian package for supporting newer Ruby versions, plus fixed to the test suite etc, and I am willing to maintain it going forward.
There is a 1.1.0 release uploaded to rubygems with those fixes, and I am now looking at the issues and pull requests from your
sup-rmail
fork. It would be nice if you could use that instead of a local fork.See terceiro/rmail
The text was updated successfully, but these errors were encountered: