-
Notifications
You must be signed in to change notification settings - Fork 37
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
in GMime 4.0, consolidate GMimeVerifyFlags and GMimeDecryptFlags as GMimeCryptoFlags #70
Comments
Do all GMimeDecryptFlags make sense for the verify function? Not sure why they should be consolidated. |
in your message on that thread, you wrote:
consolidating them into a single bitfield seems simplest to me, and the documentation could just indicate if a flag has no effect on one or the other of the operations. |
in mailing list discussion last year, i suggested consolidating GMimeVerifyFlags and GMimeDecryptFlags at the next API/ABI change.
This is just a bug report to keep track of the proposed change. (if you don't think it's a good idea, feel free to close!)
The text was updated successfully, but these errors were encountered: