12:31tokyo4j: wow this doesn't even look like a LLM answer, but just a troll
12:31tokyo4j: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/368#note_2799677
13:07llyyr: they've been spamming a bunch of wayland related repos on fd.o
13:08kennylevinsen: daniels: is that situation still in-progress?
13:13wlb: wayland-protocols Issue #242 opened by Julian Orth (mahkoh) color-management-v1: Image description types in definition of `wp_image_description_info_v1` https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/242
13:16wlb: wayland-protocols Issue #243 opened by Julian Orth (mahkoh) color-management-v1: Behavior of `get_information` for non-ready image descriptions https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/243
13:23wlb: wayland-protocols Issue #244 opened by Julian Orth (mahkoh) color-management-v1: Compositor is not required to send `wp_color_management_surface_feedback_v1::preferred_changed` event https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/244
13:29wlb: wayland-protocols Issue #243 closed \o/ (color-management-v1: Behavior of `get_information` for non-ready image descriptions https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/243)
13:51wlb: weston/main: Robert Mader * color: update color-management protocol to wp-v1 https://gitlab.freedesktop.org/wayland/weston/commit/9124a98aec8a clients/color.c clients/window.c include/libweston/libweston.h libweston/color-lcms/color-lcms.c libweston/color-lcms/color-lcms.h libweston/color-lcms/color-profile.c libweston/color-management.c libweston/color-management.h libweston/color-profile-param-
13:51wlb: weston Merge request !1689 merged \o/ (color: update color-management protocol to wp-v1 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1689)
15:56mahkoh: Is it intentional that wp_image_description_creator_params_v1::set_max_cll does not depend on any features unlink set_mastering_luminance?
21:11swick[m]: set_mastering_luminance only requires a feature for color volumes bigger than the primary, and the feature only prevents compositor defined behavior, but it's a fair question. max_cll should probably have a similar restriction.