From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnome-core: update to 45.4
Date: Wed, 28 Feb 2024 03:30:57 +0100 [thread overview]
Message-ID: <20240228023057.727CB24FCB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48752@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/48752#issuecomment-1968076680
Comment:
Some comments.
evolution, evolution-data-sever, and evolution-ews should be updated together and should be a separate PR.
grilo should be a separate PR.
gtk4 should be a separate PR.
at-spi2 should probably be a separate PR.
gnome-core should be 45.0, not 45.4.
next prev parent reply other threads:[~2024-02-28 2:30 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 0:11 [PR PATCH] gnome-core: update to 45.3 chrysos349
2024-02-16 0:18 ` chrysos349
2024-02-16 0:56 ` [PR PATCH] [Updated] " chrysos349
2024-02-16 0:56 ` chrysos349
2024-02-16 8:00 ` [PR PATCH] [Updated] " chrysos349
2024-02-16 8:12 ` chrysos349
2024-02-22 12:08 ` [PR PATCH] [Updated] gnome-core: update to 45.4 chrysos349
2024-02-22 12:11 ` chrysos349
2024-02-22 12:11 ` chrysos349
2024-02-26 7:16 ` chrysos349
2024-02-28 2:30 ` oreo639
2024-02-28 2:30 ` oreo639 [this message]
2024-02-28 5:28 ` [PR PATCH] [Updated] " chrysos349
2024-02-28 6:04 ` chrysos349
2024-02-29 20:54 ` [PR REVIEW] gnome-core: update to 45.0 oreo639
2024-03-01 4:40 ` [PR PATCH] [Updated] " chrysos349
2024-03-01 4:41 ` [PR REVIEW] " chrysos349
2024-03-04 13:20 ` oreo639
2024-03-04 13:20 ` oreo639
2024-03-04 22:22 ` oreo639
2024-03-04 22:23 ` oreo639
2024-03-05 5:27 ` [PR PATCH] [Updated] " chrysos349
2024-03-05 5:33 ` chrysos349
2024-03-05 6:20 ` chrysos349
2024-03-05 6:56 ` oreo639
2024-03-05 6:57 ` oreo639
2024-03-05 6:57 ` oreo639
2024-03-05 6:59 ` oreo639
2024-03-05 10:47 ` chrysos349
2024-03-05 11:03 ` oreo639
2024-03-05 11:04 ` oreo639
2024-03-05 14:08 ` [PR REVIEW] " oreo639
2024-03-05 14:08 ` oreo639
2024-03-05 14:09 ` oreo639
2024-03-05 15:56 ` [PR PATCH] [Updated] " chrysos349
2024-03-05 15:57 ` [PR REVIEW] " chrysos349
2024-03-05 15:57 ` chrysos349
2024-03-05 15:57 ` chrysos349
2024-03-18 4:07 ` oreo639
2024-03-18 4:07 ` oreo639
2024-03-18 13:20 ` [PR PATCH] [Updated] " chrysos349
2024-03-18 13:21 ` [PR REVIEW] " chrysos349
2024-03-19 3:45 ` oreo639
2024-03-19 4:43 ` [PR PATCH] [Updated] " chrysos349
2024-03-19 6:07 ` oreo639
2024-03-19 6:28 ` oreo639
2024-03-19 6:36 ` [PR PATCH] [Updated] " chrysos349
2024-03-19 7:28 ` oreo639
2024-03-19 7:29 ` oreo639
2024-03-19 8:42 ` [PR PATCH] [Updated] " chrysos349
2024-03-19 8:43 ` chrysos349
2024-03-19 8:47 ` chrysos349
2024-03-20 13:49 ` [PR PATCH] [Updated] " chrysos349
2024-03-20 21:29 ` [PR REVIEW] " oreo639
2024-03-20 21:42 ` oreo639
2024-03-20 21:52 ` oreo639
2024-03-20 21:53 ` oreo639
2024-03-20 21:53 ` oreo639
2024-03-20 22:00 ` [PR REVIEW] " oreo639
2024-03-20 22:01 ` oreo639
2024-03-20 22:06 ` chrysos349
2024-03-20 22:16 ` [PR PATCH] [Updated] " chrysos349
2024-03-20 22:19 ` [PR REVIEW] gnome: " chrysos349
2024-03-20 22:21 ` chrysos349
2024-03-20 22:22 ` [PR REVIEW] " oreo639
2024-03-20 22:23 ` [PR PATCH] [Updated] " chrysos349
2024-03-20 22:23 ` [PR REVIEW] " chrysos349
2024-03-20 22:40 ` oreo639
2024-03-20 22:52 ` oreo639
2024-03-20 22:56 ` oreo639
2024-03-20 23:05 ` [PR PATCH] [Updated] " chrysos349
2024-03-20 23:06 ` chrysos349
2024-03-20 23:30 ` chrysos349
2024-03-20 23:30 ` [PR REVIEW] " oreo639
2024-03-20 23:33 ` chrysos349
2024-03-21 1:57 ` [PR PATCH] [Merged]: " oreo639
2024-03-23 5:15 ` oreo639
2024-03-23 5:16 ` oreo639
2024-03-23 5:18 ` oreo639
2024-03-23 5:24 ` oreo639
2024-03-23 5:24 ` oreo639
2024-03-23 5:24 ` oreo639
2024-03-23 5:30 ` oreo639
2024-03-23 5:34 ` oreo639
2024-03-23 5:35 ` oreo639
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=20240228023057.727CB24FCB@inbox.vuxu.org \
--to=oreo639@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).