Ah typical, what a shame with all the effort and long days and nights you have spent here.
Is it worth 1. Check in a hard build error to 5,6,3 branch (pragma error) and re-tag that (with a commit to state it's a deprecated release) 2. Remove the build error and apply these fixes you have found 3. Build and tag 5.6.4 4. remove 5.6.3 zip as deprecated 5. Release 5.6.4 zip with new hashes etc. A PITA but maybe this is a sledgehammer approach but beyond re-writing git history (very bad) then perhaps this strong-arm tactic will be best. Of course somebody may have a neater solution. a soon as I get a minute or if anyone has time and experience, setting up travis, appveyor and using the travis auto check for coverity then will be a great help at catching the small stuff like this. (travis will switch on clang/gcc and clang on osx if we ask nicely) Thanks again Jeff, really appreciate what you have achieved in the last few months, well worth it. -- David Irvine twitter: @metaquestions blog: http://metaquestions.me -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
