{"push_id":971041944,"size":6,"distinct_size":6,"ref":"refs/heads/master","head":"15ed6a6c30299566afa452b9f4d14c33d1216adb","before":"67d7d2d550e81d74cdc392e360a7be5de706053f","commits":[{"sha":"8f94e967662bb5004ae5d9b5804bf7e4bb958c4c","author":{"email":"194830084ef028c9b497ad71f0a20764e5a7543c@gmail.com","name":"Philip Chimento"},"message":"coverage: Don't mangle internal coverage symbols\n\nThese symbols need to be referenced when linking to the coverage test\nprogram, so surround them with G_BEGIN_DECLS/G_END_DECLS so that they\ndon't get mangled.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=761072","distinct":true,"url":"https://api.github.com/repos/GNOME/gjs/commits/8f94e967662bb5004ae5d9b5804bf7e4bb958c4c"},{"sha":"0f92f6be86ac64c35b5671ccc05749aa9cbeeb8c","author":{"email":"194830084ef028c9b497ad71f0a20764e5a7543c@gmail.com","name":"Philip Chimento"},"message":"build: Untangle (AM_) CFLAGS, CPPFLAGS, CXXFLAGS\n\nIn Automake, CPPFLAGS stands for C PreProcessor flags. C source files are\ncompiled with CPPFLAGS and CFLAGS, while C++ source files are compiled\nwith CPPFLAGS and CXXFLAGS. The exception to this naming convention is\nthe PKG_CHECK_MODULES macro which substs a variable named <FOO>_CFLAGS\nwhich should properly be called <FOO>_CPPFLAGS.\n\nThis untangles all the flags definitions so that -I and -D flags, which\nare preprocessor arguments, are put into CPPFLAGS variables, not into\nCFLAGS or CXXFLAGS. Otherwise they won't apply to both C and C++ source\nfiles.\n\nIn addition, when using per-target flags, make sure to include the AM_\nprefixed variable as well, because otherwise per-target flags will\noverride it. Conversely, if an assignment sets a per-target flags variable\nto only be the AM_ prefixed variable (e.g., \"something_CFLAGS =\n$(AM_CFLAGS)\") then it is redundant.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=761072","distinct":true,"url":"https://api.github.com/repos/GNOME/gjs/commits/0f92f6be86ac64c35b5671ccc05749aa9cbeeb8c"},{"sha":"1b418af4a18ae0b4d1432311701cfd6e60525bda","author":{"email":"194830084ef028c9b497ad71f0a20764e5a7543c@gmail.com","name":"Philip Chimento"},"message":"tests: Don't assume localeCompare() returns +/-1\n\nPer https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/localeCompare,\n\"DO NOT rely on exact return values of -1 or 1. Negative and positive\ninteger results vary between browsers (as well as between browser\nversions) because the W3C specification only mandates negative and\npositive values. Some browsers may return -2 or 2 or even some other\nnegative or positive value.\"\n\nAnd indeed I observed this test fail with a value of -2.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=761072","distinct":true,"url":"https://api.github.com/repos/GNOME/gjs/commits/1b418af4a18ae0b4d1432311701cfd6e60525bda"},{"sha":"684fd76094344fcf2195769ed13b73531adff9e1","author":{"email":"194830084ef028c9b497ad71f0a20764e5a7543c@gmail.com","name":"Philip Chimento"},"message":"coverage test: Don't use %as specifier in sscanf()\n\n%as was a GNU extension for automatically allocating a buffer big enough\nto hold whatever string sscanf() found. In C99 %a was defined to be an\nalias of %f, so %as as a GNU extension was deprecated and made unusable.\nIt was replaced by another GNU extension, %ms.\n\nHowever, in the interests of being portable to e.g. BSD, this commit\navoids using either %as or %ms and instead pre-allocates buffers of at\nleast the correct sizes and passes them to sscanf(), using plain old %s.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=761072","distinct":true,"url":"https://api.github.com/repos/GNOME/gjs/commits/684fd76094344fcf2195769ed13b73531adff9e1"},{"sha":"7b4e0195fba61deceb3d468e76b913f9bced9b1f","author":{"email":"194830084ef028c9b497ad71f0a20764e5a7543c@gmail.com","name":"Philip Chimento"},"message":"tests: Add option not to use DBus\n\nThis adds a --without-dbus-tests configure option, which allows you to\nskip the /js/GDBus test if you don't need DBus. The default is still to\nuse DBus.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=761072","distinct":true,"url":"https://api.github.com/repos/GNOME/gjs/commits/7b4e0195fba61deceb3d468e76b913f9bced9b1f"},{"sha":"15ed6a6c30299566afa452b9f4d14c33d1216adb","author":{"email":"194830084ef028c9b497ad71f0a20764e5a7543c@gmail.com","name":"Philip Chimento"},"message":"tests: Add option not to use Xvfb\n\nNormally the tests are run under Xvfb because of needing to call\ngtk_init(); in a headless build environment this will fail if there is no\nX server.\n\nHowever, requiring Xvfb doesn't make sense if using GTK with other\nbackends than X. This adds a configure option to specify whether the\ntests should or shouldn't be run under Xvfb. The default is not to use\nXvfb, which might mean you need to configure your headless build\nenvironment to use --with-xvfb-tests.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=761072","distinct":true,"url":"https://api.github.com/repos/GNOME/gjs/commits/15ed6a6c30299566afa452b9f4d14c33d1216adb"}]}