libinput 1.11.1 is now available. A small release only with the required
fixes to update the various URLs to gitlab. Yes, you read that right,
libinput has moved from bugzilla to the freedesktop gitlab instance:
http://gitlab.freedesktop.org/libinput/libinput/
In terms of real fixes we only have
Hi Pekka!
Thank you for the feedback. In the end, I think we have a good basic
agreement about the patch, and after reading your linked bug (
https://gitlab.freedesktop.org/wayland/wayland/issues/12), which I was
previously unaware of, it sounds like I will be just stripping out the
Reviewed-by: Matheus Santana
Nice! FTP isn't even working for me (always get unauthorized).
On Mon, Jun 18, 2018 at 7:58 AM, Simon Ser wrote:
> Use a more official one, served over HTTP rather than FTP.
> ---
> doc/publican/sources/Protocol.xml | 2 +-
> 1 file changed, 1 insertion(+), 1
Reviewed-by: Matheus Santana
Thanks for engaging on this. As a newcomer, it's great to have such
information on my disposal.
On Mon, Jun 18, 2018 at 10:42 AM, Pekka Paalanen
wrote:
> From: Pekka Paalanen
>
> This has been copied from
>
Reviewed-by: Matheus Santana
It seems a great starting point.
On Mon, Jun 18, 2018 at 10:42 AM, Pekka Paalanen
wrote:
> From: Pekka Paalanen
>
> This sets up the standards for patch review, and defines when a patch
> can be merged. I believe these are the practises we have been using
>
This document might be useful for the D-Bus side:
https://dbus.freedesktop.org/doc/dbus-api-design.html
On Mon, 18 Jun 2018 at 17:05:25 +0200, Roman Gilg wrote:
> In certain high levels the compositor will ask the client through a
> special D-Bus interface to restore its internal
Hi all,
I have worked the past few days on a protocol for client session
suspension and restoration and I need to get some feedback if I'm
running in the right direction. I did get some input from Sway and
GNOME devs at the start on what they would want such a protocol to do
in general, and I did
On Monday 18 June 2018 07:48 PM, Pekka Paalanen wrote:
On Mon, 18 Jun 2018 08:58:28 -0500
Matt Hoosier wrote:
On Mon, Jun 18, 2018 at 8:54 AM Pekka Paalanen wrote:
Hi Matt,
did you intend to reply on list? Please CC if you did.
On Mon, 18 Jun 2018 08:35:56 -0500
Matt Hoosier wrote:
From: Pekka Paalanen
Now that WESTON_MODULE_MAP supersedes WESTON_BUILD_DIR for libexec
binaries, we don't need to check in WESTON_BUILD_DIR anymore.
There was only one user of weston_config_get_libexec_dir(), so remove
the whole function. There is no reason to export it.
Signed-off-by: Pekka
From: Pekka Paalanen
There are no users left.
Signed-off-by: Pekka Paalanen
---
tests/weston-tests-env | 4
1 file changed, 4 deletions(-)
diff --git a/tests/weston-tests-env b/tests/weston-tests-env
index 04648bf1..63aad4af 100755
--- a/tests/weston-tests-env
+++
From: Daniel Stone
Rename the IVI tests to be more consistent with the others, and invert
the naming of plugin/client to make it slightly more clear what's going
to happen. Handle the renaming by using wet_get_binary_path to rewrite
the local binaries.
As a side-effect, weston.ini
From: Daniel Stone
Rather than having a hardcoded dependency on the build-directory layout,
use an explicit module-map environment variable, which rewrites requests
for modules and helper/libexec binaries to specific paths.
This will help with migration to Meson where setting up the paths
From: Pekka Paalanen
Hi,
these changes are intended to make using Meson easier. Daniel's patches
are v2, mine are v1.
Daniel Stone (2):
tests: Don't rely on build directory layout
tests: Reshuffle IVI layout tests
Pekka Paalanen (2):
shared: remove weston_config_get_libexec_dir()
On Mon, 18 Jun 2018 08:58:28 -0500
Matt Hoosier wrote:
> On Mon, Jun 18, 2018 at 8:54 AM Pekka Paalanen wrote:
>
> > Hi Matt,
> >
> > did you intend to reply on list? Please CC if you did.
> >
> > On Mon, 18 Jun 2018 08:35:56 -0500
> > Matt Hoosier wrote:
> >
> > > On Mon, Jun 18, 2018 at
On Mon, Jun 18, 2018 at 8:54 AM Pekka Paalanen wrote:
> Hi Matt,
>
> did you intend to reply on list? Please CC if you did.
>
> On Mon, 18 Jun 2018 08:35:56 -0500
> Matt Hoosier wrote:
>
> > On Mon, Jun 18, 2018 at 3:59 AM Pekka Paalanen
> wrote:
> >
> > > On Mon, 18 Jun 2018 13:38:09 +0530
>
From: Pekka Paalanen
This has been copied from
https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/tree/CONTRIBUTING?id=eccae1360d6d01e73c6af2bd97122cef708207ef
and slightly edited to better with Wayland and Weston.
The intention is to make it easier to give out commit access to new
people,
From: Pekka Paalanen
Hi,
for years we have relied on unwritten traditions on how to review
patches. Gaining commit access has been a secret rite no-one really knew
what was required for to ask or grant it. I would dare claim that this
has been partially the reason for why there are so few
From: Pekka Paalanen
This sets up the standards for patch review, and defines when a patch
can be merged. I believe these are the practises we have been using
already for a long time, now they are just written down explicitly.
It's not an exhaustive list of criteria and likely cannot ever be,
On Tue, 5 Jun 2018 18:14:54 -0700
Lloyd Pique wrote:
> Introduce a new call wl_display_set_error_handler_client(), which allows
> a client to register a callback function which is invoked if there is an
> error (possibly transient) while sending messages to the server.
>
> This allows a
Use a more official one, served over HTTP rather than FTP.
---
doc/publican/sources/Protocol.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/publican/sources/Protocol.xml
b/doc/publican/sources/Protocol.xml
index 9fdee9a..fedaaab 100644
---
On Thu, 14 Jun 2018 16:49:37 +0100
Emil Velikov wrote:
> Hi all,
>
> Here's a take v2 of the series, with the following changes:
> - don't trim trailing NULL entries from the wl_interfaces* array
> - updated tests - separate patches to ease review, to be squashed
>
> On the question of why,
On Monday 18 June 2018 03:52 PM, Pekka Paalanen wrote:
On Mon, 18 Jun 2018 14:32:32 +0530
Ramalingam C wrote:
On Monday 18 June 2018 02:23 PM, Pekka Paalanen wrote:
On Mon, 18 Jun 2018 13:38:09 +0530
Ramalingam C wrote:
On Monday 18 June 2018 01:34 PM, Pekka Paalanen wrote:
On Sat,
On Mon, 18 Jun 2018 14:32:32 +0530
Ramalingam C wrote:
> On Monday 18 June 2018 02:23 PM, Pekka Paalanen wrote:
> > On Mon, 18 Jun 2018 13:38:09 +0530
> > Ramalingam C wrote:
> >
> >> On Monday 18 June 2018 01:34 PM, Pekka Paalanen wrote:
> >>> On Sat, 16 Jun 2018 12:50:52 +0530
> >>>
This adds a new protocol to negotiate server-side rendering of window
decorations for xdg-toplevels. This allows compositors that want to draw
decorations themselves to send their preference to clients, and clients that
prefer server-side decorations to request them.
This is inspired by a
This adds a new protocol to negotiate server-side rendering of window
decorations for xdg-toplevels. This allows compositors that want to draw
decorations themselves to send their preference to clients, and clients that
prefer server-side decorations to request them.
This is inspired by a
On Fri, 15 Jun 2018 16:58:38 -0300
Matheus Santana wrote:
> Replace URL for file which has been moved and remove URL for remove
> file.
>
> Signed-off-by: Matheus Santana
> ---
> architecture.html | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git
On Thu, 14 Jun 2018 18:14:14 +0100
Emil Velikov wrote:
> From: Emil Velikov
>
> Currently we issue both check and distcheck, as reportedly there has
> been cases in the past one works, while the other doesn't.
>
> Yet we only collect the check artefacts (test logs).
>
> Correct that, by
On Monday 18 June 2018 02:23 PM, Pekka Paalanen wrote:
On Mon, 18 Jun 2018 13:38:09 +0530
Ramalingam C wrote:
On Monday 18 June 2018 01:34 PM, Pekka Paalanen wrote:
On Sat, 16 Jun 2018 12:50:52 +0530
Ramalingam C wrote:
How does the kernel signal to userspace that the HDCP status has
On Mon, 18 Jun 2018 08:23:42 +0100
Emil Velikov wrote:
> On 15 June 2018 at 15:06, Maciej Wolny wrote:
> > On 05/06/18 11:53, Maciej Wolny wrote:
> >> da331647269ee9d73c4008ae901d107320bdc8d1 added a compatiblity macro for
> >> old versions of pkg-config. However, the file in which that macro
On Mon, 18 Jun 2018 13:38:09 +0530
Ramalingam C wrote:
> On Monday 18 June 2018 01:34 PM, Pekka Paalanen wrote:
> > On Sat, 16 Jun 2018 12:50:52 +0530
> > Ramalingam C wrote:
> >
> > How does the kernel signal to userspace that the HDCP status has
> > changed? Do you piggyback on the hotplug
On Sun, Jun 17, 2018 at 06:22:11PM -0400, Simon Ser wrote:
> On June 15, 2018 5:56 PM, Jonas Ådahl wrote:
> > Hi,
>
> Hi Jonas,
>
> Thanks for you feedback.
>
> > What about when clients change their "preference" in combination with a
> > window state change?
> >
> > Lets assume the compositor
On Monday 18 June 2018 01:34 PM, Pekka Paalanen wrote:
On Sat, 16 Jun 2018 12:50:52 +0530
Ramalingam C wrote:
On Friday 15 June 2018 04:16 PM, Nautiyal, Ankit K wrote:
Hi Pekka,
Thanks for the suggestions. Please find my responses inline:
On 6/15/2018 1:16 PM, Pekka Paalanen wrote:
On
On Sat, 16 Jun 2018 12:50:52 +0530
Ramalingam C wrote:
> On Friday 15 June 2018 04:16 PM, Nautiyal, Ankit K wrote:
> >
> > Hi Pekka,
> >
> > Thanks for the suggestions. Please find my responses inline:
> >
> > On 6/15/2018 1:16 PM, Pekka Paalanen wrote:
> >> On Wed, 13 Jun 2018 10:34:45 +
On 15 June 2018 at 15:06, Maciej Wolny wrote:
> On 05/06/18 11:53, Maciej Wolny wrote:
>> da331647269ee9d73c4008ae901d107320bdc8d1 added a compatiblity macro for
>> old versions of pkg-config. However, the file in which that macro
>> resides was not included. From the autoconf docs: "Note that if
34 matches
Mail list logo