From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wlroots: update to 0.17, cagebreak: update to 2.2.3
Date: Tue, 12 Dec 2023 05:57:31 +0100 [thread overview]
Message-ID: <20231212045731.Ll0q7Ue4wkCnoiqIwFFC_V73IX9nmoLUhdsXwa8UD2I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47655@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/47655#issuecomment-1851301680
Comment:
Thanks for working on this. The test failures are not significant, but they reminded me that there is not much value in moving the `wlroots` package to version 0.17 until a majority of the compositors we offer will actually use it. Therefore, I merged a subset of this PR in 2cf315d605ed and c105eb67fb9. We get the benefit of a new `wlroots0.17` and an updated `cagebreak` without needing to touch any of the other compositors.
next prev parent reply other threads:[~2023-12-12 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 21:39 [PR PATCH] wlroots: update to 0.17 migue07juegos
2023-12-08 23:31 ` [PR PATCH] [Updated] " migue07juegos
2023-12-11 16:06 ` [PR REVIEW] wlroots: update to 0.17, cagebreak: update to 2.2.3 ahesford
2023-12-11 16:06 ` ahesford
2023-12-11 16:06 ` ahesford
2023-12-11 16:18 ` ahesford
2023-12-11 16:53 ` [PR PATCH] [Updated] " migue07juegos
2023-12-11 17:01 ` [PR REVIEW] " migue07juegos
2023-12-11 18:25 ` ahesford
2023-12-11 18:51 ` ifreund
2023-12-11 19:46 ` ahesford
2023-12-11 21:00 ` [PR PATCH] [Updated] " migue07juegos
2023-12-12 4:57 ` ahesford [this message]
2023-12-12 4:57 ` [PR PATCH] [Closed]: " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231212045731.Ll0q7Ue4wkCnoiqIwFFC_V73IX9nmoLUhdsXwa8UD2I@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).