From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: [RFC] GNOME 44
Date: Sun, 18 Jun 2023 20:23:46 +0200 [thread overview]
Message-ID: <20230618182346.SFuWUrUEy-1dRiLWRez6O5qldC7wQ_jcAFrn8-bAa2s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
There's a merged pull request on the void-packages repository
[RFC] GNOME 44
https://github.com/void-linux/void-packages/pull/42965
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Depends on:
+ https://github.com/void-linux/void-packages/pull/41698
+ https://github.com/void-linux/void-packages/pull/42916
+ https://github.com/void-linux/void-packages/pull/42922
+ https://github.com/void-linux/void-packages/pull/42967
+ https://github.com/void-linux/void-packages/pull/43034
+ https://github.com/void-linux/void-packages/pull/43035
+ https://github.com/void-linux/void-packages/pull/43036
+ https://github.com/void-linux/void-packages/pull/43037
+ https://github.com/void-linux/void-packages/pull/43038
+ https://github.com/void-linux/void-packages/pull/42935
Related:
+ https://github.com/void-linux/void-packages/pull/42964
+ https://github.com/void-linux/void-packages/pull/42969
+ https://github.com/void-linux/void-packages/pull/42460
+ https://github.com/void-linux/void-packages/pull/43008
+ https://github.com/void-linux/void-packages/pull/42997
+ https://github.com/void-linux/void-packages/pull/42971
Depends on gnome-desktop 44:
+ xdg-desktop-portal-gnome
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-06-18 18:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 0:53 [PR PATCH] " oreo639
2023-03-24 0:55 ` [PR PATCH] [Updated] " oreo639
2023-03-24 10:41 ` oreo639
2023-03-26 9:45 ` [PR REVIEW] " paper42
2023-03-26 9:45 ` paper42
2023-03-26 10:39 ` [PR PATCH] [Updated] " oreo639
2023-03-26 10:40 ` [PR REVIEW] " oreo639
2023-03-26 20:25 ` [PR PATCH] [Updated] " oreo639
2023-03-26 21:35 ` oreo639
2023-03-26 21:38 ` oreo639
2023-03-26 23:24 ` oreo639
2023-03-27 23:07 ` oreo639
2023-03-27 23:11 ` oreo639
2023-03-30 23:00 ` oreo639
2023-04-03 8:45 ` oreo639
2023-04-03 8:47 ` oreo639
2023-04-03 19:18 ` oreo639
2023-04-03 19:25 ` oreo639
2023-04-07 20:38 ` oreo639
2023-04-07 20:54 ` oreo639
2023-04-07 20:56 ` oreo639
2023-04-07 22:54 ` oreo639
2023-04-28 21:19 ` oreo639
2023-06-08 8:41 ` oreo639
2023-06-08 9:12 ` oreo639
2023-06-18 13:27 ` paper42
2023-06-18 18:23 ` paper42 [this message]
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=20230618182346.SFuWUrUEy-1dRiLWRez6O5qldC7wQ_jcAFrn8-bAa2s@z \
--to=paper42@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).