From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/g-sorcery/
Date: Tue, 4 May 2021 17:57:41 +0000 (UTC) [thread overview]
Message-ID: <1620151056.e49fbd48103eaeb1c0c56bf8f359ed1b7f3a0c27.ulm@gentoo> (raw)
commit: e49fbd48103eaeb1c0c56bf8f359ed1b7f3a0c27
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue May 4 17:56:53 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue May 4 17:57:36 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e49fbd48
app-portage/g-sorcery: Fix Manifest
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
app-portage/g-sorcery/Manifest | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-portage/g-sorcery/Manifest b/app-portage/g-sorcery/Manifest
index 66c68bc0b03..562db957c0f 100644
--- a/app-portage/g-sorcery/Manifest
+++ b/app-portage/g-sorcery/Manifest
@@ -1,2 +1,2 @@
DIST g-sorcery-0.2.1.tar.gz 55546 BLAKE2B 56fb8a766c17c220a8279d2288f5de5c6976dc8fb380ac695bcf891616aa8a284f6b07c9be79c3c819c69faf7fcf9a7a826ee8b8b955db007c00e23d6417f2f8 SHA512 42c34ed8addaf721583029d5056751810b0a77546f798081c7c605223342fa2a99bd2e30f20f004a8606ccf847108f0e2ef2c479f3cbb55f2fe6648d4ffc075e
-DIST g-sorcery-0.2.2.tar.gz 55694 BLAKE2B dade6853f23176a020c337aad418f84a26d7227b544ad33ec60fee6a3454cb1b6c75a3bad659a18e18447ccaa4a3fd02d59a3eb12fed5dfd877ef0b787807364 SHA512 a858737c5034d33205b293ecde69dd84a2abb533a3dad1e076a30cfadbf594e454250b71cbd8acc37025ee78c720092bd3edefb69d45cd760c6f91c8bae4f539
+DIST g-sorcery-0.2.2.tar.gz 55707 BLAKE2B 59466e116caff697618154f3c9d8a2c11809ac0c1d367a35a7773fdcad381e283c2426310ccd4f843e10e6fc5143061f2ee575bdd190a1a51d7691be0d452d73 SHA512 a63b6a49225fbf5105666a6d8094f04534674c4773eb8008e2cb8e2eb75291011d53ff3f1bf6dd456496469d537a97151feca73b9b26553cf1fda9d3128534cb
next reply other threads:[~2021-05-04 17:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 17:57 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-21 5:35 [gentoo-commits] repo/gentoo:master commit in: app-portage/g-sorcery/ Sam James
2023-05-19 16:39 Ulrich Müller
2023-05-19 16:39 Ulrich Müller
2023-05-19 16:39 Ulrich Müller
2023-02-25 16:09 Ulrich Müller
2023-02-24 18:17 Ulrich Müller
2023-02-24 18:17 Ulrich Müller
2022-07-16 5:06 Ulrich Müller
2022-06-03 21:01 Arthur Zamarin
2021-09-14 14:15 Yixun Lan
2021-05-23 10:11 Michał Górny
2021-05-04 17:27 Ulrich Müller
2021-05-04 17:27 Ulrich Müller
2020-10-07 14:11 Brian Dolbec
2020-08-16 9:57 Michał Górny
2020-04-24 23:37 Brian Dolbec
2020-02-26 12:18 Michał Górny
2020-02-13 10:42 Michał Górny
2019-05-18 10:02 Michał Górny
2019-02-09 20:12 Aaron Bauman
2018-10-16 9:18 Tobias Klausmann
2018-06-27 19:29 Pacho Ramos
2018-03-28 5:42 Matt Turner
2018-03-21 18:12 Michał Górny
2018-03-18 11:00 Sergei Trofimovich
2018-02-22 7:55 Sergei Trofimovich
2018-02-11 10:25 Michał Górny
2017-04-06 6:41 Michael Weber
2017-03-23 17:05 Markus Meier
2016-12-24 22:31 Brian Dolbec
2016-08-08 1:57 Benda XU
2016-01-18 21:04 Jauhien Piatlicki
2015-10-10 9:20 Markus Meier
2015-09-19 18:45 Mike Gilbert
2015-08-22 21:52 Jauhien Piatlicki
2015-08-18 10:58 Jauhien Piatlicki
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=1620151056.e49fbd48103eaeb1c0c56bf8f359ed1b7f3a0c27.ulm@gentoo \
--to=ulm@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