{"push_id":549044462,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"0a0fbce38c655efd09a74b0a8532fe426e34caef","before":"246d7ab6a13b10eff27724ab4fecfeb05b7d60ae","commits":[{"sha":"2c49ef93c6bd58adc1e2101dc949ae10802b7cf9","author":{"email":"f594c690101f9f56fcbe8e1c82c05c46bc81ffdf@over-yonder.net","name":"Matthew D. Fuller"},"message":"Don't bother testing indirectly for int128 support around here.\n\nThe condition is pointless; on the one hand, Build will have failed if it\ncouldn't figure out a way to to int128, so we wouldn't even get to\ncompiling.  Further, it doesn't work right anyway, since it's testing for\nsomething pretending to be gcc 4.4+, whereas clang builds supporting\nint128 don't necessary make that claim.","distinct":true,"url":"https://api.github.com/repos/fullermd/MaxMind-DB-Reader-XS/commits/2c49ef93c6bd58adc1e2101dc949ae10802b7cf9"},{"sha":"0a0fbce38c655efd09a74b0a8532fe426e34caef","author":{"email":"f594c690101f9f56fcbe8e1c82c05c46bc81ffdf@over-yonder.net","name":"Matthew D. Fuller"},"message":"Flip around these conditions for how we setup int128_t.\n\n__SIZEOF_INT128__ should absolutely signify its presence.  GCC 4.6+ and\nclang 3.2+ should have it even if that's not defined (on platforms where\nit's supported, but if it weren't, Build.PL would have failed already).","distinct":true,"url":"https://api.github.com/repos/fullermd/MaxMind-DB-Reader-XS/commits/0a0fbce38c655efd09a74b0a8532fe426e34caef"}]}