{"push_id":1361873297,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"2d4b2f14d09abc3088ac56fe6af2dcb3da86ee47","before":"1ee329d6173f6dd923283c2149872f98aa5c5116","commits":[{"sha":"13e6b151b04566271b785bb47268096a6b0c159b","author":{"name":"DRC","email":"769b217ebcd46641135d96e5d66e3e1516881dd5@libjpeg-turbo.org"},"message":"Win: Use YASM if it is in the PATH and NASM isn't\n\nPreviously, simd/CMakeLists.txt was hard-coded to use NASM, and it was\nnecessary to override the NASM variable in order to use YASM.  This\ncommit changes the behavior such that NASM is still preferred, but YASM\nwill be used if it is in the PATH and NASM isn't available.  This brings\nthe actual behavior in line with the behavior described in BUILDING.md.\n\nBased on\nhttps://github.com/xpol/libjpeg-turbo/commit/b0799a1598782799d4876538eddca7ad8438d8a6\n\nCloses #107","distinct":true,"url":"https://api.github.com/repos/mayeut/libjpeg-turbo/commits/13e6b151b04566271b785bb47268096a6b0c159b"},{"sha":"9366cf0bca7dc511c66533c1b733a16d323ce145","author":{"name":"DRC","email":"769b217ebcd46641135d96e5d66e3e1516881dd5@libjpeg-turbo.org"},"message":"Travis: GPG sign Linux binaries/source tarballs\n\nSince we're still deploying our Linux/macOS CI artifacts to a web server\n(specifically SourceForge Project Web Services) that doesn't support\nHTTPS, it's a good idea to sign them.  But since the private key has to\nbe checked into the repository, we use a different key for signing the\npre-releases (per project policy, the private signing keys for our\nrelease binaries are never made available on any public server.)","distinct":true,"url":"https://api.github.com/repos/mayeut/libjpeg-turbo/commits/9366cf0bca7dc511c66533c1b733a16d323ce145"},{"sha":"2d4b2f14d09abc3088ac56fe6af2dcb3da86ee47","author":{"name":"DRC","email":"769b217ebcd46641135d96e5d66e3e1516881dd5@libjpeg-turbo.org"},"message":"Travis: Deploy to S3 rather than SourceForge\n\nThis has the following advantages:\n-- It doesn't require checking a private SSH key into the repository.\n(With SourceForge, an SSH key is the \"keys to the kingdom\".)\n-- If the S3 key is compromised, it is very easy to revoke it and\ngenerate a new one.\n-- The S3 bucket is isolated, so even if it becomes compromised, then\nthe damage that one could do is limited.\n-- It's much easier to manage files through S3's web interface than\nthrough SourceForge.\n-- The files are served via HTTPS.\n-- Travis fully supports S3 as a deployment target, so this simplifies\n.travis.yml somewhat.","distinct":true,"url":"https://api.github.com/repos/mayeut/libjpeg-turbo/commits/2d4b2f14d09abc3088ac56fe6af2dcb3da86ee47"}]}
{"actor":{"display_login":"mayeut"}}