From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] wlroots: update to 0.9.1
Date: Tue, 21 Jan 2020 01:48:34 +0100 [thread overview]
Message-ID: <20200121004834.GnylI4nL662BI4G2m4hU03UMhGLsORiqd39MZcc3kOw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18432@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/18432#issuecomment-576472934
Comment:
Yep, do the ones you can. Leave it open so that people know it's being worked on while you wait.
However there are some patches already avaliable in master which you can add to the patches/ subdirectory for each package:
- Sway: https://github.com/swaywm/sway/commit/ed02261551ac7748d38af4a0bcdeeab0437571fe -- adding .patch to the end gives you a patch you can use https://github.com/swaywm/sway/commit/ed02261551ac7748d38af4a0bcdeeab0437571fe.patch
- Cage: https://github.com/Hjdskes/cage/commit/51e6c760da51e2b885737d61a61cdc965bb9269d and https://github.com/Hjdskes/cage/commit/bfd7d605b89fc5436505611ad01806fc11aa9a08.
For future reference, I found these by going to the github repositories and searching for wlroots in commits.
next prev parent reply other threads:[~2020-01-21 0:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 20:34 [PR PATCH] " voidlinux-github
2020-01-20 20:44 ` voidlinux-github
2020-01-20 20:52 ` voidlinux-github
2020-01-20 20:54 ` voidlinux-github
2020-01-20 21:01 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20 21:02 ` voidlinux-github
2020-01-20 21:37 ` voidlinux-github
2020-01-20 21:39 ` voidlinux-github
2020-01-20 21:47 ` voidlinux-github
2020-01-20 22:06 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20 22:32 ` [WIP] " voidlinux-github
2020-01-20 22:32 ` voidlinux-github
2020-01-20 22:33 ` voidlinux-github
2020-01-21 0:48 ` voidlinux-github [this message]
2020-01-21 8:41 ` voidlinux-github
2020-01-21 8:41 ` voidlinux-github
2020-01-21 12:58 ` voidlinux-github
2020-01-21 14:15 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-21 16:07 ` voidlinux-github
2020-01-21 16:15 ` voidlinux-github
2020-01-21 16:20 ` voidlinux-github
2020-01-21 16:26 ` voidlinux-github
2020-01-21 16:29 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-22 20:14 ` voidlinux-github
2020-01-22 20:40 ` voidlinux-github
2020-01-22 20:44 ` voidlinux-github
2020-01-22 21:18 ` voidlinux-github
2020-01-22 21:23 ` voidlinux-github
2020-01-22 21:25 ` voidlinux-github
2020-01-22 21:26 ` voidlinux-github
2020-01-22 21:35 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-22 22:07 ` voidlinux-github
2020-01-22 22:11 ` voidlinux-github
2020-01-23 6:00 ` voidlinux-github
2020-01-23 7:43 ` voidlinux-github
2020-01-23 8:01 ` [PR PATCH] [Updated] (WIP) wlroots: update to 0.10.0 voidlinux-github
2020-01-23 8:25 ` voidlinux-github
2020-01-23 8:35 ` voidlinux-github
2020-01-23 8:54 ` voidlinux-github
2020-01-25 7:51 ` [PR PATCH] [Merged]: wlroots: update to 0.10.0, cage: revbump, wayfire: update to 0.3.1, sway: update to 1.4 voidlinux-github
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=20200121004834.GnylI4nL662BI4G2m4hU03UMhGLsORiqd39MZcc3kOw@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).