{"push_id":1017926654,"size":64,"distinct_size":64,"ref":"refs/heads/master","head":"0715ee5cf9c467b0aa2717f6276716d81fd0178b","before":"389c84e24868d68141364093ad0acd372c6195f4","commits":[{"sha":"3384f69ecf043d62a4e036c0353c2daa01d7c4d0","author":{"email":"2f97e0f0bc172406aab8ccd42dab54c95bab8759@osg.samsung.com","name":"Derek Foreman"},"message":"protocol: Add wl_surface.damage_buffer\n\nwl_surface.damage uses surface local co-ordinates.\n\nBuffer scale and buffer transforms came along, and EGL surfaces\nhave no understanding of them.\n\nTheoretically, clients pass damage rectangles - in Y-inverted surface\nco-ordinates) to EGLSwapBuffersWithDamage, and the EGL implementation\npassed them on to wayland.  However, for this to work the EGL\nimplementation must be able to flip those rectangles into the space\nthe compositor is expecting, but it's unable to do so because it\ndoesn't know the height of the transformed buffer.\n\nSo, currently, EGLSwapBuffersWithDamage is unusable and EGLSwapBuffers\nhas to pass (0,0) - (INT32_MAX, INT32_MAX) damage to function.\n\nwl_surface.damage_buffer allows damage to be registered on a surface\nin buffer co-ordinates, avoiding this problem.\n\nCredit where it's due, these ideas are not entirely my own:\nOver a year ago the idea of changing damage co-ordinates to buffer\nco-ordinates was suggested (by Jason Ekstrand), and it was at least\npartially rejected and abandoned.  At the time it was also suggested\n(by Pekka Paalanen) that adding a new wl_surface.damage_buffer request\nwas another option.\n\nThis will eventually resolve:\nhttps://bugs.freedesktop.org/show_bug.cgi?id=78190\nby making the problem irrelevant.\n\nReviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>\nReviewed-by: Jason Ekstrand <jason@jlekstrand.net>\nSigned-off-by: Derek Foreman <derekf@osg.samsung.com>\nReviewed-by: Jonas Ådahl <jadahl@gmail.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/3384f69ecf043d62a4e036c0353c2daa01d7c4d0"},{"sha":"87321d0f2fb61a3808e7a0cc1d71f82d065b2cd2","author":{"email":"b9c50af7afa7642f6f854434cda9ffe54ece8b85@who-t.net","name":"Peter Hutterer"},"message":"protocol: specify behavior of get_pointer when capabilities change\n\nAlso applies to touch/keyboard\n\nSigned-off-by: Peter Hutterer <peter.hutterer@who-t.net>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>\nReviewed-by: Jonas Ådahl <jadahl@gmail.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/87321d0f2fb61a3808e7a0cc1d71f82d065b2cd2"},{"sha":"225830dcb8bf1a6583d0f4ca182584024783923e","author":{"email":"bdb14cfc1ab8d24e13de84adc40b41ae60c13bd1@osg.samsung.com","name":"Bryce Harrington"},"message":"server: Add a socket with an existing fd\n\nThis adds functionality to allow system-level control over handing out\nfile descriptors for sockets, to allow tighter security when running a\nWayland compositor under a Wayland session server.  Allows writing\nsocket activated Wayland servers.\n\nSigned-off-by: Bryce Harrington <bryce@osg.samsung.com>\nReviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>\nCc: Sung-Jin Park <sj76.park@samsung.com>\nCc: Sangjin Lee <lsj119@samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/225830dcb8bf1a6583d0f4ca182584024783923e"},{"sha":"2f666ee34fb414f43def75c1caa1243feb349f8d","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"scanner: Add missing brackets\n\nA statement was added at the same indentation level as the true branch\nof the if statement, but since there were no brackets, it would be\nexecuted independently of the result of the if condition.\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Marek Chalupa <mchqwerty@gmail.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/2f666ee34fb414f43def75c1caa1243feb349f8d"},{"sha":"3de1783e5038639128bb37f2937eeee3e36aefe6","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"scanner: Fail if 'since' is higher than the interface version\n\nIf an event or request have a \"since\" attribute that is larger than\nthe version of the interface it is in, fail with an explaining error\nmessage.\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Marek Chalupa <mchqwerty@gmail.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/3de1783e5038639128bb37f2937eeee3e36aefe6"},{"sha":"2e7fb786825472d2a4b717e0b82d216aa90fb3e0","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"Use zalloc instead of malloc + memset\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Marek Chalupa <mchqwerty@gmail.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/2e7fb786825472d2a4b717e0b82d216aa90fb3e0"},{"sha":"edbee66cbd11f2b186831ac6c92937f638586961","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"doc: Fix function membership\n\nPut the various misplaced functions in the right class; partly because\nits where they belong, and partly to make intra-class \\ref(erences)\nhappy.\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/edbee66cbd11f2b186831ac6c92937f638586961"},{"sha":"ee9b69cfe0c94a297e1dea7cc4ff147d740c4294","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"doc: Fix incorrect parameter name\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Marek Chalupa <mchqwerty@gmail.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/ee9b69cfe0c94a297e1dea7cc4ff147d740c4294"},{"sha":"0a37511ecc0117339e5e5d0add84a2f3b51493d2","author":{"email":"0c33b8cd8f82c4833188d6ead21812b7b1d34705@lge.com","name":"Jaeyoon Jung"},"message":"server: Calculate remaining data size after a closure is processed\n\nWhen processing a closure, data in the connection can be consumed again\nif the closure itself invokes extra event dispatch. In that case the\nremaining data size is also altered, so the variable len should be\nupdated after the closure is processed.\n\nSigned-off-by: Jaeyoon Jung <jaeyoon.jung@lge.com>\nReviewed-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/0a37511ecc0117339e5e5d0add84a2f3b51493d2"},{"sha":"693bf00083c372de4da785810429498d215d0c85","author":{"email":"f9b08f8e7fafc600b4001b40e111bccb07507c72@m4x.org","name":"Victor Berger"},"message":"client: Add missing arg in a wl_log invocation\n\nWithout this 'proxy' argument, the '%p' formatter prints a constant\ngarbage value.\n\nSigned-off-by: Victor Berger <victor.berger@m4x.org>\nReviewed-by: Marek Chalupa <mchqwerty@gmail.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/693bf00083c372de4da785810429498d215d0c85"},{"sha":"1b7191743eeeecedd66af03eeb960c5978fc8335","author":{"email":"a05df156a69ad59faa9af9b666ef78009594c145@gmail.com","name":"Marek Chalupa"},"message":"server: don't send an error to NULL display_resource\n\nif display_resource = wl_resource_create() fails in bind_display(),\nwe call wl_client_post_no_memory() which is wrong, since this function\nuses display_resource (which is NULL at this point).\nsaid simply: don't send an error to resource that you've just failed to create)\n\nhttps://bugs.freedesktop.org/show_bug.cgi?id=91356\n\nReported-by: Ashim <ashim.shah@samsung.com>\nSigned-off-by: Marek Chalupa <mchqwerty@gmail.com>\nReviewed-by: Derek Foreman <derekf@osg.samsung.com>\nReviewed-by: Bryce Harrington <bryce@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/1b7191743eeeecedd66af03eeb960c5978fc8335"},{"sha":"69a5a6d16c3ce97d6032ad61ba3503c8e598d359","author":{"email":"bdb14cfc1ab8d24e13de84adc40b41ae60c13bd1@osg.samsung.com","name":"Bryce Harrington"},"message":"socket-test: Fix some comment typos\n\nSigned-off-by: Bryce Harrington <bryce@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/69a5a6d16c3ce97d6032ad61ba3503c8e598d359"},{"sha":"2b236af9b7f21b81df9ded062921da6cc3f37eb9","author":{"email":"bdb14cfc1ab8d24e13de84adc40b41ae60c13bd1@osg.samsung.com","name":"Bryce Harrington"},"message":"socket-test: Refactor if check into the assert\n\nSigned-off-by: Bryce Harrington <bryce@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/2b236af9b7f21b81df9ded062921da6cc3f37eb9"},{"sha":"c5356e9016aa814a873a765bb2cbe57e804e5ea7","author":{"email":"b9c50af7afa7642f6f854434cda9ffe54ece8b85@who-t.net","name":"Peter Hutterer"},"message":"protocol: add wl_pointer.frame, axis_source, axis_stop, and axis_discrete\n\nThe frame event groups separate pointer events together. The primary use-case\nfor this at the moment is diagonal scrolling - a vertical/horizontal scroll\nevent can be grouped together to calculate the correct motion vector.\nFrame events group all wl_pointer events. An example sequence of motion events\nfollowed by a diagonal scroll followed by a button event is:\nwl_pointer.motion\nwl_pointer.frame\nwl_pointer.motion\nwl_pointer.frame\nwl_pointer.axis\nwl_pointer.axis\nwl_pointer.frame\nwl_pointer.button\nwl_pointer.frame\n\nIn the future, other extensions may insert additional information about an\nevent into the frame. For example, an extension may add information about the\nphysical device that generated an event into the frame. For this reason,\nenter/leave events are grouped by a frame event too.\n\nThe axis_source event determines how an axis event was generated. That enables\nclients to judge when to use kinetic scrolling. Only one axis_source event is\nallowed per frame and applies to all events in this frame.\n\nThe axis_stop event notifies a client about the termination of a scroll\nsequence, likewise needed to calculate kinetic scrolling parameters.\nMultiple axis_stop events within the same frame indicate that scrolling has\nstopped in all these axis at the same time.\n\nThe axis_discrete event provides the wheel click count. Previously the axis\nvalue was some hardcoded number (10), with the discrete steps this enables a\nclient to differ between line-based scrolling on a mouse wheel and smooth\nscrolling with a touchpad. The axis_discrete event carries the axis\ninformation and the discrete value and can occur at any time in the frame\nprovided it is ordered before the matching axis event. Specifically, this\nsequence is valid:\n\nwl_pointer.axis_source\nwl_pointer.axis_discrete (vert)\nwl_pointer.axis_discrete (horiz)\nwl_pointer.axis (horiz)\nwl_pointer.axis (vert)\nwl_pointer.frame\n\nEnter and leave event also trigger wl_pointer.frame events, where possible the\ncompositor should group leave and subsequent enter into the same frame. This\nindicates to the client that the pointer has moved between surfaces and may\nallow a client to shortcut code otherwise triggerd by the leave or enter\nevents.\n\nSigned-off-by: Peter Hutterer <peter.hutterer@who-t.net>\nReviewed-by: Carlos Garnacho <carlosg@gnome.org>\nReviewed-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>\nReviewed-by: Bryce Harrington <bryce@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/c5356e9016aa814a873a765bb2cbe57e804e5ea7"},{"sha":"16b4cc6902e2755522ce792ee2796df487c0860a","author":{"email":"2f97e0f0bc172406aab8ccd42dab54c95bab8759@osg.samsung.com","name":"Derek Foreman"},"message":"server: improve failure log message for wl_global_create()\n\nThe gratuitous %m jammed onto the end of the string prints errno\nconcatenated with the word \"version\".\n\nI've removed the %m, and printed some additional information about the\nfailure.\n\nAlso, reversed the order of the expressions in the conditional to\nmake it match the english in the log message.\n\nSigned-off-by: Derek Foreman <derekf@osg.samsung.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/16b4cc6902e2755522ce792ee2796df487c0860a"},{"sha":"2b4c053924150d6652c42aa28ce70d173757ab0b","author":{"email":"2f97e0f0bc172406aab8ccd42dab54c95bab8759@osg.samsung.com","name":"Derek Foreman"},"message":"server: Test for illegally low interface versions in wl_global_create()\n\nAny version lower than 1 is unreasonable.\n\nSigned-off-by: Derek Foreman <derekf@osg.samsung.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/2b4c053924150d6652c42aa28ce70d173757ab0b"},{"sha":"5c4272b8e9b16d632e89f1e9448abc370b957443","author":{"email":"8aa797d77d86809a7bc4a8544e3c327451cf6b4f@gnome.org","name":"Carlos Garnacho"},"message":"protocol: Improve data source notification around DnD progress\n\nCurrently, there's no means for the DnD origin to know whether the\ndestination is actually finished with the DnD transaction, short of\nfinalizing it after the first transfer finishes, or leaking it forever.\n\nBut this poses other interoperation problems, drag destinations might\nbe requesting several mimetypes at once, might be just poking to find\nout the most suitable format, might want to defer the action to a popup,\nmight be poking contents early before the selection was dropped...\n\nIn addition, data_source.cancelled is suitable for the situations where\nthe DnD operation fails (not on a drop target, no matching mimetypes,\netc..), but seems undocumented for that use (and unused in weston's DnD).\n\nIn order to improve the situation, the drag source should be notified\nof all stages of DnD. In addition to documenting the \"cancelled\" event\nfor DnD purposes, The following 2 events have been added:\n\n- wl_data_source.dnd_drop_performed: Happens when the operation has been\n  physically finished (eg. the button is released), it could be the right\n  place to reset the pointer cursor back and undo any other state resulting\n  from the initial button press.\n- wl_data_source.dnd_finished: Happens when the destination side destroys\n  the wl_data_offer, at this point the source can just forget all data\n  related to the DnD selection as well, plus optionally deleting the data\n  on move operations.\n\nChanges since v6:\n  - Turned wl_data_offer.finish calls with 0/NULL state/mimetype an\n    error, made it explicit that it will only result in\n    wl_data_offer.dnd_finished being sent if successful.\n\nChanges since v5:\n  - Further rewording of wl_data_offer.finish and wl_data_offer.accept.\n    Added error for untimely wl_data_offer.finish requests.\n\nChanges since v4:\n  - Applied rewording suggestions from Jonas Ådahl. Added new\n    wl_data_offer.finish request to allow explicit finalization on the\n    destination side.\n\nChanges since v3:\n  - Renamed dnd_performed to a more descriptive dnd_drop_performed,\n    documented backwards compatible behavior on wl_data_offer.accept and\n    wl_data_source.cancelled.\n\nChanges since v2:\n  - Minor rewording.\n\nChanges since v1:\n  - Renamed events to have a common \"dnd\" namespace. Made dnd_performed to\n    happen invariably, data_device.cancelled may still happen afterwards.\n\nSigned-off-by: Carlos Garnacho <carlosg@gnome.org>\nReviewed-by: Michael Catanzaro <mcatanzaro@igalia.com>\nReviewed-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Mike Blumenkrantz <zmike@samsung.com>\nReviewed-by: Bryce Harrington <bryce@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/5c4272b8e9b16d632e89f1e9448abc370b957443"},{"sha":"da7b2489041ef465158601087ed0ef6d2e68445d","author":{"email":"8aa797d77d86809a7bc4a8544e3c327451cf6b4f@gnome.org","name":"Carlos Garnacho"},"message":"protocol: Add DnD actions\n\nThese 2 requests have been added:\n\n- wl_data_source.set_actions: Notifies the compositor of the available\n  actions on the data source.\n- wl_data_offer.set_actions: Notifies the compositor of the available\n  actions on the destination side, plus the preferred action.\n\nOut of the data from these requests, the compositor can determine the action\nboth parts agree on (and let the user play a role through eg. keyboard\nmodifiers). The chosen option will be notified to both parties\nthrough the following two requests:\n\n- wl_data_source.action\n- wl_data_offer.action\n\nIn addition, the destination side can peek the source side actions through\nwl_data_offer.source_actions.\n\nCompared to the XDND protocol, there's two notable changes:\n\n- XDND lets the source suggest an action, whereas wl_data_device lets\n  the destination prefer a given action. The difference is subtle here,\n  it comes off as convenience because it is the drag destination which\n  receives the motion events (unlike in X) and can perform action updates.\n\n  The drag destination seems also in a better position to update the\n  preferred action based on things like the data being transferred, the\n  place being dropped, and whether the drag is client-local.\n\n- That same source-side preferred action is used in XDND to convey the\n  modifier-induced action to the drag destination, which would then ack\n  it, or reply with another action that's accepted (or none), this makes\n  the XdndPosition/XdndStatus messaging very verbose, and synchronous\n  because the drag source always needs to know the latest status/action\n  for every position+action sent.\n\n  Here it's the compositor which takes care of modifiers and matching\n  available/accepted actions, this allows for the signaling to happen\n  only whenever the actions/modifiers change for real.\n\nRoughly based on previous work by Giulio Camuffo <giuliocamuffo@gmail.com>\n\nChanges since v10:\n- Narrow down the situations where wl_data_source/offer.accept requests\n  are supposed to happen.\n\nChanges since v9:\n- Deferred the protocol errors to .finish after some IRC chat with Jonas,\n  added further errors if actions API is used on selection sources/offers.\n\nChanges since v8:\n- Defined further the expected behavior on \"ask\", described the protocol\n  errors that may happen. Fix more spaces vs tabs issues.\n\nChanges since v7:\n- Misc changes after updating the progress notification patch.\n\nChanges since v6:\n- Further explanations on wl_data_source/offer.set_actions, including a\n  description of \"ask\" actions. Added protocol errors for unknown action\n  values.\n\nChanges since v5:\n- Applied rewording suggestions from Jonas Ådahl. Dropped slot reservation\n  scheme for actions. Fixed indentation and other minor formatting issues.\n\nChanges since v4:\n- Minor rewording.\n\nChanges since v3:\n- Splitted from DnD progress notification changes.\n- Further rationales in commit log.\n\nChanges since v2:\n- Renamed notify_actions to set_actions on both sides, seems more consistent\n  with the rest of the protocol.\n- Spelled out better which events may be triggered on the compositor side\n  by the requests, the circumstances in which events are emitted, and\n  what are events useful for in clients.\n- Defined a minimal common ground wrt compositor-side action picking and\n  keybindings.\n- Acknowledge the possibility of compositor/toolkit defined actions, even\n  though none are used at the moment.\nChanges since v1:\n- Added wl_data_offer.source_actions to let know of the actions offered\n  by a data source.\n- Renamed wl_data_source.finished to \"drag_finished\" for clarity\n- Improved wording as suggested by Bryce\n\nSigned-off-by: Carlos Garnacho <carlosg@gnome.org>\nReviewed-by: Michael Catanzaro <mcatanzaro@igalia.com>\nReviewed-by: Mike Blumenkrantz <zmike@samsung.com>\nReviewed-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Bryce Harrington <bryce@osg.samsung.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/da7b2489041ef465158601087ed0ef6d2e68445d"},{"sha":"0edeeb9cd5806959660af54d63fe9d402d50e6e7","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"client: Correct documentation regarding thread safeness\n\nThe current documentation about wl_display_dispatch() states one may not\nmix wl_display_dispatch(_queue)() with wl_display_prepare_read() and\nfriends, but this is a misconception about how\nwl_display_dispatch(_queue)() works. The fact is that the dispatch\nfunctions does the equivalent of what the preparation API does\ninternally, and it is safe to use together.\n\nWhat is not safe is to dispatch using the wl_display_dispatch(_queue)()\nfunctions while being prepared to read using wl_display_read_events().\n\nThis patch rewrites the documentation to correctly state when the\nvarious API's are thread safe and how they may not be used.\n\nhttps://bugs.freedesktop.org/show_bug.cgi?id=91767\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Daniel Stone <daniels@collabora.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/0edeeb9cd5806959660af54d63fe9d402d50e6e7"},{"sha":"0b44298a15674121ff54585c706bfdefc0d9942a","author":{"email":"67dcd8a17e758192e0cbb577ce1d62cc7da6cf49@gmail.com","name":"Jonas Ådahl"},"message":"client: Remove misplaced documentation about main loop intergration\n\nThere was documentation about how to integrate the display server file\ndescriptor in the documentation about wl_display_dispatch_pending().\nThis is not the right place to put it, and it also had incorrect usage\nof the API (calling wl_display_dispatch_queue() on input on an unrelated\nfd) as an example.\n\nSigned-off-by: Jonas Ådahl <jadahl@gmail.com>\nReviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>\nReviewed-by: Daniel Stone <daniels@collabora.com>","distinct":true,"url":"https://api.github.com/repos/sir-murray/wayland/commits/0b44298a15674121ff54585c706bfdefc0d9942a"}]}