From: "Zhang Zheng" <zhangzheng.dylan@foxmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: games-action/ddnet/
Date: Wed, 26 Oct 2022 07:30:57 +0000 (UTC) [thread overview]
Message-ID: <1666769436.a3421a510d0e8336f3859035c66d6706aba24fba.zhangzheng.dylan@gentoo> (raw)
commit: a3421a510d0e8336f3859035c66d6706aba24fba
Author: Big Pineapple <zhangzheng.dylan <AT> foxmail <DOT> com>
AuthorDate: Wed Oct 26 07:30:36 2022 +0000
Commit: Zhang Zheng <zhangzheng.dylan <AT> foxmail <DOT> com>
CommitDate: Wed Oct 26 07:30:36 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=a3421a51
games-action/ddnet: add 16.5, drop 16.4
Signed-off-by: Big Pineapple <zhangzheng.dylan <AT> foxmail.com>
games-action/ddnet/Manifest | 2 +-
games-action/ddnet/{ddnet-16.4.ebuild => ddnet-16.5.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/games-action/ddnet/Manifest b/games-action/ddnet/Manifest
index 3efea2392..6d2d52e4d 100644
--- a/games-action/ddnet/Manifest
+++ b/games-action/ddnet/Manifest
@@ -1 +1 @@
-DIST ddnet-16.4.tar.gz 35885750 BLAKE2B 0ed16b83f1b4327f3bac0687372bdcdf362385ac5e553ab62c0bf80e853a0f3a3dee46e3a114b61e462de60794b7e08c77d9000eba31bba867c73612e68e5c64 SHA512 a1215f052a42e346510c2303dcf008f00b78bd99fa869ff65b8383c473c3d09fd53066264ba826f0a4462232f9ad860792a1d5f8fd96417d3118f311e527070d
+DIST ddnet-16.5.tar.gz 35864109 BLAKE2B a85cc2ef89f8e9d84a17bf7e1c49262409e09d0a386ea5ff47a7aee08ef71ac2a4f76bc487894404477c4ce150b10461324b4c5363c34edf4d18dbc2d1d0dbea SHA512 5a96aa960fcea1c217a2f1beb5ce6dd0f7350668b3155095618fbdb794b8a7fc173264367038e066ad558ebcde27a697ce0ded6ff37eed10e273e2b434cfe6a7
diff --git a/games-action/ddnet/ddnet-16.4.ebuild b/games-action/ddnet/ddnet-16.5.ebuild
similarity index 100%
rename from games-action/ddnet/ddnet-16.4.ebuild
rename to games-action/ddnet/ddnet-16.5.ebuild
next reply other threads:[~2022-10-26 7:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 7:30 Zhang Zheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-25 14:22 [gentoo-commits] repo/proj/guru:dev commit in: games-action/ddnet/ Edgar Luque
2025-02-25 14:22 Edgar Luque
2025-01-09 16:19 Edgar Luque
2024-12-27 8:53 Edgar Luque
2024-11-10 14:46 Edgar Luque
2024-10-10 8:20 Edgar Luque
2024-09-19 13:32 Edgar Luque
2024-09-09 14:39 Edgar Luque
2024-07-24 7:24 Edgar Luque
2024-07-07 13:32 Edgar Luque
2024-05-03 8:20 Edgar Luque
2024-03-19 10:32 Edgar Luque
2024-02-01 7:12 Edgar Luque
2023-12-18 8:39 Edgar Luque
2023-12-18 8:39 Edgar Luque
2023-12-18 8:25 Edgar Luque
2023-12-15 12:49 Edgar Luque
2023-11-20 10:23 Edgar Luque
2023-09-27 11:11 Edgar Luque
2023-08-28 9:47 Edgar Luque
2023-08-17 11:47 Edgar Luque
2023-07-09 13:24 Edgar Luque
2023-07-07 11:09 Edgar Luque
2023-06-07 11:38 Edgar Luque
2023-06-01 9:27 Zhang Zheng
2023-05-28 8:43 Edgar Luque
2023-05-25 14:08 Edgar Luque
2023-04-03 6:27 Edgar Luque
2023-03-10 11:28 Edgar Luque
2023-03-05 14:14 Edgar Luque
2023-02-01 7:48 Edgar Luque
2022-12-28 12:42 Zhang Zheng
2022-12-12 15:35 Edgar Luque
2022-12-12 15:01 Edgar Luque
2022-12-12 15:00 Edgar Luque
2022-11-10 20:55 Edgar Luque
2022-11-10 20:55 Edgar Luque
2022-09-23 3:01 Zhang Zheng
2022-09-13 6:45 Zhang Zheng
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=1666769436.a3421a510d0e8336f3859035c66d6706aba24fba.zhangzheng.dylan@gentoo \
--to=zhangzheng.dylan@foxmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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