From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: net-im/discord-canary-bin/
Date: Fri, 20 Dec 2024 00:36:28 +0000 (UTC) [thread overview]
Message-ID: <1734633001.69cb3d678bc2e74b17f745a91c807a119fb50d9e.davidroman@gentoo> (raw)
commit: 69cb3d678bc2e74b17f745a91c807a119fb50d9e
Author: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 19 18:29:43 2024 +0000
Commit: David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Thu Dec 19 18:30:01 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=69cb3d67
net-im/discord-canary-bin: add 0.0.549, drop 0.0.306
Signed-off-by: Viorel Munteanu <ceamac <AT> gentoo.org>
net-im/discord-canary-bin/Manifest | 2 +-
...cord-canary-bin-0.0.306.ebuild => discord-canary-bin-0.0.549.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-im/discord-canary-bin/Manifest b/net-im/discord-canary-bin/Manifest
index 6a50378cb..7015891a0 100644
--- a/net-im/discord-canary-bin/Manifest
+++ b/net-im/discord-canary-bin/Manifest
@@ -1 +1 @@
-DIST discord-canary-0.0.306.deb 100786292 BLAKE2B 052bb4c8f452b9015c603a648099b3f8447aa4082091ba417ac84bde03a690e347931ed615f18677d4103e7c7e680ab57bbb388fb8169e5a26ef5b54182d84d5 SHA512 6b5aa78862ca33a1ee35f47766321502734ed62af42496e7167237bbb54417e1379e435cbada7557d28b940f7e405cecbe680a3812a8b3d2f7d292f1d376cfeb
+DIST discord-canary-0.0.549.deb 101350134 BLAKE2B 99d92cf1d1939388b06fc0a869a0ae97b44ba3b966a0cd02a3e959921822d2acc7c14f369588fceb963879869527a6be05ced0d20512e9436994e58ac668feff SHA512 c602ee180578bee9df64bdafeeda5c48b465d26f199e3c695243f14b37ee26d8064a78d35e5871336228f625c13b6864d36be64da2ff5468aea097a0206751b2
diff --git a/net-im/discord-canary-bin/discord-canary-bin-0.0.306.ebuild b/net-im/discord-canary-bin/discord-canary-bin-0.0.549.ebuild
similarity index 100%
rename from net-im/discord-canary-bin/discord-canary-bin-0.0.306.ebuild
rename to net-im/discord-canary-bin/discord-canary-bin-0.0.549.ebuild
next reply other threads:[~2024-12-20 0:36 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 0:36 David Roman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-21 12:04 [gentoo-commits] repo/proj/guru:master commit in: net-im/discord-canary-bin/ David Roman
2025-02-10 9:42 David Roman
2025-01-30 15:26 David Roman
2024-03-15 7:10 Rui Huang
2024-01-25 10:49 David Roman
2024-01-19 10:31 Arthur Zamarin
2024-01-15 15:46 David Roman
2024-01-11 11:57 David Roman
2024-01-08 7:18 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2024-01-08 7:22 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2024-01-04 15:19 Viorel Munteanu
2023-12-21 6:32 Viorel Munteanu
2023-12-18 6:33 Viorel Munteanu
2023-12-15 6:02 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-12-15 6:03 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-12-14 7:25 Viorel Munteanu
2023-12-12 6:19 Viorel Munteanu
2023-12-11 6:50 Viorel Munteanu
2023-12-11 6:50 Viorel Munteanu
2023-12-04 7:11 Viorel Munteanu
2023-12-04 6:37 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-12-04 7:11 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-12-02 1:29 Haelwenn Monnier
2023-08-18 6:21 Viorel Munteanu
2023-08-18 6:16 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-08-18 6:21 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-08-17 5:15 Viorel Munteanu
2023-08-17 5:09 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-08-17 5:15 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-08-10 8:14 Viorel Munteanu
2023-08-10 8:14 Viorel Munteanu
2023-07-12 8:47 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-07-12 8:47 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-07-12 8:47 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-07-12 8:47 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-05-27 6:10 Viorel Munteanu
2023-05-27 6:10 Viorel Munteanu
2023-03-12 9:14 Viorel Munteanu
2023-02-14 12:02 Florian Schmaus
2023-02-13 11:28 Andrew Ammerlaan
2023-01-14 18:43 Andrew Ammerlaan
2022-12-07 19:50 Ronny Gutbrod
2022-12-07 19:50 Ronny Gutbrod
2022-09-06 1:06 Ronny Gutbrod
2022-05-28 10:10 Andrew Ammerlaan
2022-03-07 21:21 Ronny Gutbrod
2022-01-12 15:20 Florian Schmaus
2021-09-23 6:45 Arthur Zamarin
2021-09-20 9:17 Andrew Ammerlaan
2021-08-27 16:10 Haelwenn Monnier
2021-06-30 7:14 Florian Schmaus
2021-06-29 6:59 Florian Schmaus
2021-06-04 7:59 Andrew Ammerlaan
2021-05-24 7:31 Andrew Ammerlaan
2021-05-22 12:16 Andrew Ammerlaan
2021-05-14 19:08 Andrew Ammerlaan
2021-05-14 17:17 Andrew Ammerlaan
2021-03-24 9:05 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-03-24 9:05 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-02-19 10:14 Michał Górny
2020-12-18 15:25 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-12-18 16:26 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-11-12 19:46 Andrew Ammerlaan
2020-08-09 21:00 Andrew Ammerlaan
2020-06-09 15:52 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-06-09 16:37 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-05-11 8:57 Andrew Ammerlaan
2020-05-11 8:57 Andrew Ammerlaan
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=1734633001.69cb3d678bc2e74b17f745a91c807a119fb50d9e.davidroman@gentoo \
--to=davidroman96@gmail.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