From: "Nick Sarnie" <sarnex@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/discord/
Date: Tue, 14 Nov 2023 01:54:25 +0000 (UTC) [thread overview]
Message-ID: <1699926853.1838d81a1a0bb23039297e7c2bc14bce9739279a.sarnex@gentoo> (raw)
commit: 1838d81a1a0bb23039297e7c2bc14bce9739279a
Author: Tomas Fabrizio Orsi <torsi <AT> fi <DOT> uba <DOT> ar>
AuthorDate: Mon Nov 13 22:46:38 2023 +0000
Commit: Nick Sarnie <sarnex <AT> gentoo <DOT> org>
CommitDate: Tue Nov 14 01:54:13 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1838d81a
net-im/discord: add 0.0.35, drop 0.0.34
Signed-off-by: Tomas Fabrizio Orsi <torsi <AT> fi.uba.ar>
Closes: https://github.com/gentoo/gentoo/pull/33810
Signed-off-by: Nick Sarnie <sarnex <AT> gentoo.org>
net-im/discord/Manifest | 2 +-
net-im/discord/{discord-0.0.34.ebuild => discord-0.0.35.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-im/discord/Manifest b/net-im/discord/Manifest
index 06d5c8184763..bcb9c6636d20 100644
--- a/net-im/discord/Manifest
+++ b/net-im/discord/Manifest
@@ -1 +1 @@
-DIST discord-0.0.34.tar.gz 92968432 BLAKE2B 0db1f1459169a7de36733dddf2a945b136fa854d73abbd72648fc3c46c0ec82ae81f944a228bf4d4d876cbed4924fc34d5eb81af989309d76adc8148883a9b1c SHA512 28ab59e18ca3c800030c7c4b4f016efed033e741ad42f18b993e8493d51a78d430a4ff3c0a3457fdf8b43907a013f3145e67748e7a896d440af56074226c5c46
+DIST discord-0.0.35.tar.gz 92973520 BLAKE2B ed0c72d39e2da6afb640926e5b96b6a6a689d7f82908898c7622aa9ba74dfbec16746178f17b294017d40a0ede376cd86580fd37b64c6be42c423c43b61dbf02 SHA512 a0f1db24e38a2d48ea8521a7e8e638a401bdfc407b64e21c7a0dde241eb10e4988fcdc916ed13d45012ae4ce25b3c53d36bf97b011cf569cb81e9f1b7c2d6eeb
diff --git a/net-im/discord/discord-0.0.34.ebuild b/net-im/discord/discord-0.0.35.ebuild
similarity index 100%
rename from net-im/discord/discord-0.0.34.ebuild
rename to net-im/discord/discord-0.0.35.ebuild
next reply other threads:[~2023-11-14 1:54 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 1:54 Nick Sarnie [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-25 20:06 [gentoo-commits] repo/gentoo:master commit in: net-im/discord/ Nick Sarnie
2024-11-19 7:06 Nick Sarnie
2024-11-13 6:30 Nick Sarnie
2024-11-04 19:25 Nick Sarnie
2024-10-22 11:18 Nick Sarnie
2024-10-10 8:35 Nick Sarnie
2024-10-02 5:12 Nick Sarnie
2024-09-24 4:42 Nick Sarnie
2024-09-10 6:37 Nick Sarnie
2024-09-04 19:38 Nick Sarnie
2024-09-02 1:39 Nick Sarnie
2024-08-28 6:51 Nick Sarnie
2024-08-22 23:27 Nick Sarnie
2024-08-13 18:42 Nick Sarnie
2024-08-06 0:20 Nick Sarnie
2024-07-30 22:07 Nick Sarnie
2024-07-22 22:42 Nick Sarnie
2024-07-15 23:37 Nick Sarnie
2024-07-09 23:52 Nick Sarnie
2024-06-30 18:57 Nick Sarnie
2024-06-26 0:48 Nick Sarnie
2024-06-24 22:16 Nick Sarnie
2024-06-17 18:32 Nick Sarnie
2024-06-11 0:07 Nick Sarnie
2024-06-05 2:19 Nick Sarnie
2024-05-14 17:54 Nick Sarnie
2024-05-07 6:17 Joonas Niilola
2024-04-29 22:46 Nick Sarnie
2024-04-23 0:24 Nick Sarnie
2024-04-17 11:08 Joonas Niilola
2024-04-09 19:23 Nick Sarnie
2024-04-09 1:11 Nick Sarnie
2024-03-26 10:08 Nick Sarnie
2024-03-19 11:44 Nick Sarnie
2024-03-13 10:00 Nick Sarnie
2024-03-12 17:39 Nick Sarnie
2024-03-07 3:12 Nick Sarnie
2024-02-13 3:33 Nick Sarnie
2024-01-29 21:37 Nick Sarnie
2024-01-23 3:53 Nick Sarnie
2024-01-10 17:10 Nick Sarnie
2023-12-21 7:52 Sam James
2023-12-12 23:06 Nick Sarnie
2023-12-05 22:19 Nick Sarnie
2023-11-28 23:23 Nick Sarnie
2023-11-07 1:44 Nick Sarnie
2023-10-31 18:03 Nick Sarnie
2023-10-17 0:52 Nick Sarnie
2023-10-05 19:46 Nick Sarnie
2023-09-18 23:08 Stefan Strogin
2023-08-30 20:22 Nick Sarnie
2023-07-12 8:32 Stefan Strogin
2023-05-10 14:02 Ionen Wolkens
2023-05-10 14:02 Ionen Wolkens
2023-04-27 22:44 Nick Sarnie
2023-04-27 14:41 Pacho Ramos
2023-03-31 16:25 Sam James
2023-03-31 16:23 Sam James
2023-03-31 0:44 Nick Sarnie
2023-02-14 1:24 Stefan Strogin
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=1699926853.1838d81a1a0bb23039297e7c2bc14bce9739279a.sarnex@gentoo \
--to=sarnex@gentoo.org \
--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