From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: godot: update to 4.0.3.
Date: Mon, 03 Jul 2023 14:19:41 +0200 [thread overview]
Message-ID: <20230703121941.5OVdyP1qenwpcsHL5AXlt3DGcTBRsG-mCmJFhCr_9EM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41675@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
There's a merged pull request on the void-packages repository
godot: update to 4.0.3.
https://github.com/void-linux/void-packages/pull/41675
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
**Godot 4.0 is released!**
Please test the PR on different architectures and give feedback here about the usability.
next prev parent reply other threads:[~2023-07-03 12:19 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 8:14 [PR PATCH] [WIP] New package: godot-beta dataCobra
2023-01-16 8:16 ` classabbyamp
2023-01-18 8:59 ` [PR PATCH] [Updated] [WIP] Draft for change from Godot 3 to 4 dataCobra
2023-01-18 8:59 ` dataCobra
2023-03-01 17:16 ` lun-4
2023-03-01 17:31 ` dataCobra
2023-03-01 17:32 ` dataCobra
2023-03-01 18:18 ` [PR PATCH] [Updated] " dataCobra
2023-03-01 19:16 ` [PR PATCH] [Updated] Upgrade Godot from " dataCobra
2023-03-01 19:18 ` dataCobra
2023-03-01 19:19 ` [PR PATCH] [Updated] " dataCobra
2023-03-01 19:21 ` dataCobra
2023-03-01 19:23 ` dataCobra
2023-03-05 19:52 ` jstnas
2023-03-08 6:29 ` [PR PATCH] [Updated] " dataCobra
2023-03-08 6:30 ` dataCobra
2023-03-08 18:36 ` jstnas
2023-03-09 8:17 ` dataCobra
2023-03-21 0:22 ` zen0bit
2023-03-21 12:59 ` jstnas
2023-03-21 13:38 ` eljamm
2023-03-21 18:18 ` jstnas
2023-03-23 6:23 ` [PR PATCH] [Updated] " dataCobra
2023-03-23 6:25 ` dataCobra
2023-03-23 6:32 ` dataCobra
2023-03-23 6:33 ` [PR PATCH] [Updated] " dataCobra
2023-03-23 6:34 ` dataCobra
2023-03-23 13:43 ` dataCobra
2023-03-23 16:55 ` fgietzen
2023-03-24 1:50 ` zen0bit
2023-03-24 1:53 ` zen0bit
2023-03-24 1:53 ` zen0bit
2023-03-26 16:37 ` Newchair2644
2023-03-26 16:40 ` Newchair2644
2023-03-28 9:54 ` eljamm
2023-03-28 9:55 ` eljamm
2023-03-29 2:52 ` Newchair2644
2023-03-29 12:30 ` eljamm
2023-04-12 8:08 ` [PR PATCH] [Updated] " dataCobra
2023-04-12 8:11 ` godot: update to 4.0.2 dataCobra
2023-04-12 8:12 ` dataCobra
2023-04-12 12:56 ` eljamm
2023-05-14 7:33 ` [PR PATCH] [Updated] " dataCobra
2023-05-15 5:37 ` dataCobra
2023-05-25 15:12 ` [PR PATCH] [Updated] " dataCobra
2023-05-25 15:39 ` dataCobra
2023-05-27 18:18 ` godot: update to 4.0.3 bilebucket
2023-05-28 13:26 ` eljamm
2023-06-02 12:50 ` obunden
2023-06-04 8:04 ` bilebucket
2023-06-12 7:45 ` [PR PATCH] [Updated] " dataCobra
2023-06-16 11:30 ` dataCobra
2023-06-16 11:45 ` [PR REVIEW] " leahneukirchen
2023-06-16 11:50 ` dataCobra
2023-06-25 18:25 ` [PR PATCH] [Updated] " dataCobra
2023-06-27 8:30 ` dataCobra
2023-06-27 8:37 ` [PR REVIEW] " dataCobra
2023-06-27 8:38 ` dataCobra
2023-06-27 16:23 ` leahneukirchen
2023-06-27 18:39 ` [PR PATCH] [Updated] " dataCobra
2023-06-27 18:42 ` [PR REVIEW] " dataCobra
2023-06-29 6:21 ` [PR PATCH] [Updated] " dataCobra
2023-06-29 13:15 ` leahneukirchen
2023-06-29 13:45 ` [PR PATCH] [Updated] " dataCobra
2023-06-29 13:46 ` dataCobra
2023-06-29 13:53 ` dataCobra
2023-06-29 13:53 ` dataCobra
2023-07-01 6:23 ` astralchan
2023-07-01 6:25 ` astralchan
2023-07-01 6:34 ` [PR REVIEW] " astralchan
2023-07-01 6:38 ` astralchan
2023-07-01 6:50 ` astralchan
2023-07-01 14:38 ` leahneukirchen
2023-07-01 14:46 ` dataCobra
2023-07-01 14:53 ` leahneukirchen
2023-07-01 15:06 ` dataCobra
2023-07-02 7:05 ` dataCobra
2023-07-02 7:07 ` dataCobra
2023-07-02 7:08 ` dataCobra
2023-07-02 7:09 ` [PR PATCH] [Updated] " dataCobra
2023-07-02 7:12 ` dataCobra
2023-07-02 7:17 ` dataCobra
2023-07-02 8:45 ` dataCobra
2023-07-02 8:45 ` dataCobra
2023-07-03 12:19 ` leahneukirchen [this message]
2023-07-04 3:59 ` [PR REVIEW] " astralchan
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=20230703121941.5OVdyP1qenwpcsHL5AXlt3DGcTBRsG-mCmJFhCr_9EM@z \
--to=leahneukirchen@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).