From: "Anna Vyalkova" <cyber+gentoo@sysrq.in>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/got/
Date: Sun, 30 Oct 2022 08:38:48 +0000 (UTC) [thread overview]
Message-ID: <1667119116.745ff57525a4e43fb8aa1192835db380f3d02ec8.cybertailor@gentoo> (raw)
commit: 745ff57525a4e43fb8aa1192835db380f3d02ec8
Author: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Sun Oct 30 08:36:33 2022 +0000
Commit: Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Sun Oct 30 08:38:36 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=745ff575
dev-vcs/got: add 0.77, drop 0.74
Signed-off-by: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq.in>
dev-vcs/got/Manifest | 2 +-
dev-vcs/got/{got-0.74.ebuild => got-0.77.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-vcs/got/Manifest b/dev-vcs/got/Manifest
index 5f1c14916..a48601857 100644
--- a/dev-vcs/got/Manifest
+++ b/dev-vcs/got/Manifest
@@ -1,2 +1,2 @@
-DIST got-portable-0.74.tar.gz 756603 BLAKE2B 1ed8df3d792b125ad2c55618373f2d0456f86ccacb7c83446cab8a6c3f2ae30774e065d31e9bddb4ad0b9c5b0d65b0430be80b8c510d3132817bc0d95180f0ba SHA512 eb513783953871c6e76075ed15486ac91538248479844b6feec6c9282e520a6e1a052d39d379dd1ec8a760730e1110f997dc48be06e31c644054f3a6e873f9b8
DIST got-portable-0.76.tar.gz 842394 BLAKE2B a2fa8ee75c7934f4b2dd901c95c54e7ba4c4ec36007fcd4912b7ae78cec83cc1baa0e9553ec13cd7e0aaaf884291d9087c544da7c7cb071c7bf90bdee4c7287f SHA512 c51bc6a6d537c12f9437e3dab44779157a56aea6dea4a3ad222c53406f3ea5f2215d9a1ccd75496fcf60fb3b69e50572e89b82024f1195b8a57993e92bbc068f
+DIST got-portable-0.77.tar.gz 860031 BLAKE2B 51bcac0d7393a5620d542c23db0a25db6ebcc4ea32faa18f08d59b6567721a4611ee7dbc0fd7b718810ba5e694b91209f7e645c54328255364caff224efc2841 SHA512 7135d63077457abf8320924ba1ec3586f4ae9d32fce2fe9493325765934f2d8c023ea399ba875c8f27d3e95437d1940bc60b4df8669060c3171cbc4df8103ce8
diff --git a/dev-vcs/got/got-0.74.ebuild b/dev-vcs/got/got-0.77.ebuild
similarity index 100%
rename from dev-vcs/got/got-0.74.ebuild
rename to dev-vcs/got/got-0.77.ebuild
next reply other threads:[~2022-10-30 8:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 8:38 Anna Vyalkova [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-21 18:00 [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/got/ Anna Vyalkova
2023-06-30 16:28 Anna Vyalkova
2023-06-10 10:35 Anna Vyalkova
2023-05-09 13:21 Anna Vyalkova
2023-05-08 16:45 Anna Vyalkova
2023-04-27 19:29 Anna Vyalkova
2023-03-16 13:09 Anna Vyalkova
2023-03-08 17:27 Anna Vyalkova
2023-02-24 21:31 Anna Vyalkova
2023-02-24 21:31 Anna Vyalkova
2023-02-15 13:56 Anna Vyalkova
2023-01-26 20:53 Anna Vyalkova
2022-11-10 18:17 Anna Vyalkova
2022-11-04 15:24 Anna Vyalkova
2022-11-03 3:09 Anna Vyalkova
2022-10-08 14:58 Anna Vyalkova
2022-08-04 13:10 Anna Vyalkova
2022-07-07 2:57 Anna Vyalkova
2022-06-25 21:29 Anna Vyalkova
2022-05-30 19:26 Anna Vyalkova
2022-03-31 7:24 Anna Vyalkova
2022-02-23 13:44 Anna Vyalkova
2022-01-16 17:58 Anna Vyalkova
2022-01-07 15:18 Anna Vyalkova
2021-11-25 7:16 Anna Vyalkova
2021-10-17 16:34 Anna Vyalkova
2021-10-17 10:30 Anna Vyalkova
2021-09-23 14:19 Anna Vyalkova
2021-08-08 12:59 Anna Vyalkova
2021-08-04 6:13 Anna Vyalkova
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=1667119116.745ff57525a4e43fb8aa1192835db380f3d02ec8.cybertailor@gentoo \
--to=cyber+gentoo@sysrq.in \
--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