From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: net-im/discord-canary-bin/
Date: Sat, 28 May 2022 10:10:19 +0000 (UTC) [thread overview]
Message-ID: <1653606595.e96f08eeb4140f6669f8bf78f2cb0a6d5cd34ec3.andrewammerlaan@gentoo> (raw)
commit: e96f08eeb4140f6669f8bf78f2cb0a6d5cd34ec3
Author: Marcin Woźniak <y0rune <AT> aol <DOT> com>
AuthorDate: Thu May 26 23:09:26 2022 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Thu May 26 23:09:55 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e96f08ee
net-im/discord-canary-bin: Upgraded from 0.0.134 -> 0.0.135
Signed-off-by: Marcin Woźniak <y0rune <AT> aol.com>
net-im/discord-canary-bin/Manifest | 2 +-
...cord-canary-bin-0.0.134.ebuild => discord-canary-bin-0.0.135.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 dec98a595..1c0d8c51f 100644
--- a/net-im/discord-canary-bin/Manifest
+++ b/net-im/discord-canary-bin/Manifest
@@ -1 +1 @@
-DIST discord-canary-0.0.134.deb 77138802 BLAKE2B d7d76f88a8b501c29f0684ee9e754d692e2fa9c2b6248c411f692588f6e535efef36ebab0ca00b9b318011ebf113aea6b12f772f576be9f3ec9215be6832b736 SHA512 26fe257ca4e331bc5a3be64dc757c7b8944eb443e407be1095e238df527ef686be5f0a2c078d907b525232cac378278cb3972c54265ca361b84fc35c0c5d2a75
+DIST discord-canary-0.0.135.deb 77137258 BLAKE2B f3fb10c340fb97098d43cd9229d134a1e75a2bfbbe84572e9c4923a5511c056e4251e9509ca80457cb8e2559fa6f00d0a62130cd96d6588f47b3cdc7fc76458f SHA512 f76311ceb914d5db74632e029e037fad84ff562727f747ad23520c2ae2da7b7cdaa2e1cf5887964aeefa4fb819f846ecc7c35e15b0ff2a592c7e871248c99fe8
diff --git a/net-im/discord-canary-bin/discord-canary-bin-0.0.134.ebuild b/net-im/discord-canary-bin/discord-canary-bin-0.0.135.ebuild
similarity index 100%
rename from net-im/discord-canary-bin/discord-canary-bin-0.0.134.ebuild
rename to net-im/discord-canary-bin/discord-canary-bin-0.0.135.ebuild
next reply other threads:[~2022-05-28 10:10 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 10:10 Andrew Ammerlaan [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-12-20 0:36 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-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=1653606595.e96f08eeb4140f6669f8bf78f2cb0a6d5cd34ec3.andrewammerlaan@gentoo \
--to=andrewammerlaan@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