{"push_id":771252864,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"018a068e3380297a797ea8283a923eeea0431cea","before":"adc1afb303d32ddadf325906f7d675c3321b9ab3","commits":[{"sha":"4c17c6a0dd224b66379c52ea8b24ab961b908aa0","author":{"email":"d08020ea5f4e6f367280328bfd8afcf523970e19@gmail.com","name":"Jason Gerecke"},"message":"Update release.sh script from Xorg\n\nThe latest-and-greatest copy of release.sh from Xorg now replaces our\ncurrent version of the script which largely dates back to 2010. This\nscript brings several new features along with it, with stronger checks\nand PGP signing probably being the two worth noting.\n\nA very small number of modifications to the upstream version of this\nscript (commit 65cb27b) have been made to support this project. The only\none of note is a change to 'generate_announce' which changes it to\nuse the 'Reply-To' header instead of 'Cc' (since the announce list will\nbounce unauthorized messages back).\n\nSigned-off-by: Jason Gerecke <jason.gerecke@wacom.com>\nAcked-by: Peter Hutterer <peter.hutterer@who-t.net>","distinct":true,"url":"https://api.github.com/repos/antigol/xf86-input-wacom/commits/4c17c6a0dd224b66379c52ea8b24ab961b908aa0"},{"sha":"9e216247b549f95c0511b5b3243e1527cabcb161","author":{"email":"d08020ea5f4e6f367280328bfd8afcf523970e19@gmail.com","name":"Jason Gerecke"},"message":"Don't rely on IsPad() when trying to undo kernel event filtering\n\nCommit e9f95de fixed an issue where the pointer would jump around if the\nkernel's duplicate event filtering had removed the X or Y position from\nthe initial \"entering proximity\" packet. The fix involved requesting the\ncurrent axis value from the kernel, but only if we weren't dealing with\nthe pad (since the pad never sends position data, and may not even have\nthose axes). Unfortunately, the check used 'IsPad(priv)', which may\nreturn incorrect results at this point in the program flow.* This can\ncause the pointer jumps to occur anyway if the driver (incorrectly)\nbelieves the events to be coming from the pad as described in bug #286.\n\nTo fix this, the check is changed to rely on 'ds->device_type' which\nprovides accurate information.\n\n*It appears that the 'pInfo' passed into 'usbDispatchEvents' may be of\nany X device that shares the same underlying kernel device. It is not\nuntil later in 'wcmEvent' that we use 'findTool' to find the appropriate\ndevice based on the 'ds->device_type'.\n\nhttp://sourceforge.net/p/linuxwacom/bugs/286/\n\nSigned-off-by: Jason Gerecke <jason.gerecke@wacom.com>","distinct":true,"url":"https://api.github.com/repos/antigol/xf86-input-wacom/commits/9e216247b549f95c0511b5b3243e1527cabcb161"},{"sha":"018a068e3380297a797ea8283a923eeea0431cea","author":{"email":"d9fae29ec0b0b1b21639eb845e9bc51db666b5eb@gmail.com","name":"Mario Geiger"},"message":"Merge branch 'master' of git://git.code.sf.net/p/linuxwacom/xf86-input-wacom","distinct":true,"url":"https://api.github.com/repos/antigol/xf86-input-wacom/commits/018a068e3380297a797ea8283a923eeea0431cea"}]}