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: Mon, 8 May 2023 16:45:35 +0000 (UTC) [thread overview]
Message-ID: <1683563639.e1d52cf49d898ffa3bb89f6ecfd053ab70fb3b3b.cybertailor@gentoo> (raw)
commit: e1d52cf49d898ffa3bb89f6ecfd053ab70fb3b3b
Author: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Mon May 8 16:33:59 2023 +0000
Commit: Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Mon May 8 16:33:59 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e1d52cf4
dev-vcs/got: add 0.88, drop 0.86
Signed-off-by: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq.in>
dev-vcs/got/Manifest | 2 +-
dev-vcs/got/{got-0.86.ebuild => got-0.88.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-vcs/got/Manifest b/dev-vcs/got/Manifest
index 38cc72572..a58f200c5 100644
--- a/dev-vcs/got/Manifest
+++ b/dev-vcs/got/Manifest
@@ -1,2 +1,2 @@
-DIST got-portable-0.86.tar.gz 1034905 BLAKE2B f04eaa87fb3dfd0c2bf8e9d4557c5f7d5b75c601744fb6be2622e8d3ba67702ed5c9f45117f57c60fedb86dfb6c2ebb63596dc53182fa6410639e0a3a038c11b SHA512 adc40c9197b18cdb78bdd962e962ebe2b120552377ad3d9a92acae77182939c06e7cd386bc0b7f4b0970752a9ea9736eb4af98096be7062fa12630dd9f452b4b
DIST got-portable-0.87.tar.gz 1047429 BLAKE2B 76be96d8fc1cecffe670401010ebb5454c8ed351b30623c66160605dda8b989237cc4a53f1f6233937a7a5c51b95771b2b207c0c57e6f45ce19cd5d1aa22d509 SHA512 a752830f22e484485b67178d2470a77852985bedb4df16c3dc9a0c2e1d07f4e2fddec854b1cb6ddd6427bc8d3d386c4e6b9b2b6c9e38dbe26718ef89190a5602
+DIST got-portable-0.88.tar.gz 1048477 BLAKE2B fde36ce7895d67010e07671666b549f51055215aa025c24b3f4652c3ecc039d04b316f7f751ea6e96a9a39907aac1abcaf98b4bd35f632011892443e998663cd SHA512 91d01043468304dbbafdcbf999fa234b0cf5b4e2bd4267728874910f71984b0f05de0cde90c8183f1e0634ee5815bd6ba842d595eaaabe95d84d23fc5706011c
diff --git a/dev-vcs/got/got-0.86.ebuild b/dev-vcs/got/got-0.88.ebuild
similarity index 100%
rename from dev-vcs/got/got-0.86.ebuild
rename to dev-vcs/got/got-0.88.ebuild
next reply other threads:[~2023-05-08 16:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:45 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-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-30 8:38 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=1683563639.e1d52cf49d898ffa3bb89f6ecfd053ab70fb3b3b.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