13:51bl4ckb0ne: is there a rule to merge non new protocol mr in wayland-protocols?
13:51bl4ckb0ne: like minimum amount of ack/lgtm from members required
13:51emersion: ah, so updates to an existing protocol?
13:52emersion: we've used the same rules
13:52emersion: same # of acks, same # of impls
13:52bl4ckb0ne: so there would be one more lgtm for !261
13:53emersion: i wish we had a bot expanding MR refs in here :P
13:53bl4ckb0ne: time to bring your bot from wlroots
13:54emersion: ah, if it's just a clarification, then no need
13:54emersion: better wait a few days to see if anybody else has something to say
13:54bl4ckb0ne:merges away
13:54wlb: wayland-protocols/main: Simon Ser * presentation-time: stop referring to Linux/glibc https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/87e0ce44f32e stable/presentation-time/presentation-time.xml
13:54wlb: wayland-protocols Merge request !261 merged \o/ (presentation-time: stop referring to Linux/glibc https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/261)
13:54bl4ckb0ne: would be nice to have the rule somewhere
13:55bl4ckb0ne: woops
13:55bl4ckb0ne: alt tabbed before seeing your message
13:57Ermine: Can't wlb expand mr refs?
13:57emersion: nope :(
13:58Ermine: Well, are there wlb sources?
13:59pq: Regardless of the change, one should always let an upstream protocol patch soak at least a few days.
14:01emersion: yeah
14:02daniels: Ermine: iirc it's https://github.com/sardemff7/eventd/tree/master/plugins/webhook
14:03daniels: if someone comes up with fixes for it then SardemFF7 is the one to ping; if there's a better alternative I'll happily get it configured on the GitLab side to use it
14:03SardemFF7: it’s actually a chain of https://clients.eventd.org/git/ + https://www.eventd.org/ with the libpurple plugin :-)
14:04SardemFF7: Ermine: what do you mean “expand mr refs”?
14:06Ermine: SardemFF7: if someone writes !123, bot posts description and link to wayland-protocols merge request 123
14:06emersion: we use https://gitlab.freedesktop.org/emersion/glhf for #wlroots
14:07pq: why wayland-protocols and not wayland MR?
14:07pq: the project to look in needs to be explicit
14:07emersion: yeah, such as w-p#123
14:08pq: also weston and libinput are in scope on this channel
14:08Ermine: One project could be configured as default
14:08Ermine: I only gave an example
14:09daniels: pq: wayland, wp, libinput, xkbcommon, weston, wlr, mutter, kwin, etc
14:10daniels: emersion: if you've already got it set up tho and it already supports multiple projects, maybe you could just throw it in here?
14:10emersion: vyivel did the work to support multiple projects
14:10emersion: ah, i suppose i can turn it on, and not use the event delivery part
14:13SardemFF7: Ermine: oh, that
14:13SardemFF7: it’s not actually a bot
14:13SardemFF7: I could add some sort of support for that kind of things, but never had use for it
14:26pq: swick[m], btw. are you intentionally trying to leave MR branches existing after merged into 'color' in your fork? I've been merging with auto-delete.
14:26swick[m]: no, don't mind it
14:27pq: cool, just wanted to check you don't want to keep them as backups
23:02wlb: weston Issue #835 opened by Michael Karlesky (mkarlesky) “error: color operations capability missing. Is GL-renderer not in use?” when GL-renderer is in use. https://gitlab.freedesktop.org/wayland/weston/-/issues/835