On Sun, Nov 22, 2015 at 10:20 PM, Mobile Mouse <mouse...@gmail.com> wrote: > I think this is the right way to deal with the situation at hand.
Yeah, this was an uncomfortable spot. The revert, clean commit and re-tagging was required to ensure users experienced as little pain as possible. It also satisfies change control systems, where folks may have to go back in time deterministically. In one week or one year, it will still be correct. I hope Wei dies not start questioning our abilities to self govern.... Sadly, it will be my fault if he takes it away from us. I hope it does not come to that. Jeff > On Nov 22, 2015, at 20:12, Jeffrey Walton <noloa...@gmail.com> wrote: > > Hi Everyone, > > I talked with Wei about this. We basically took option (2) below. First we > started with a fresh ZIP file. Next we reverted the bad check-ins from both > Sourceforge and GitHub. We followed with a commit of the un-corrupted files. > Finally, we tagged the commits as CRYPTOPP_5_6_3. > -- -- 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.
