public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anna Vyalkova" <cyber+gentoo@sysrq.in>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-nim/cligen/
Date: Sun, 25 Dec 2022 02:19:36 +0000 (UTC)	[thread overview]
Message-ID: <1671934760.e57a5ad8d87d97e9520034576dbf232f07584111.cybertailor@gentoo> (raw)

commit:     e57a5ad8d87d97e9520034576dbf232f07584111
Author:     Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Fri Dec 23 22:15:13 2022 +0000
Commit:     Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Sun Dec 25 02:19:20 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e57a5ad8

dev-nim/cligen: add 1.5.33, drop 1.5.30

Signed-off-by: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq.in>

 dev-nim/cligen/Manifest                                       | 2 +-
 dev-nim/cligen/{cligen-1.5.30.ebuild => cligen-1.5.33.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-nim/cligen/Manifest b/dev-nim/cligen/Manifest
index d4f602555..e3219283f 100644
--- a/dev-nim/cligen/Manifest
+++ b/dev-nim/cligen/Manifest
@@ -1,2 +1,2 @@
-DIST cligen-1.5.30.tar.gz 425024 BLAKE2B 5737d1279bbdf1b2b1135d0cae0637a55279b93e0761368b7d551b6f85f1410a97ae7761390eb0c332ac39b60d551f1be2fd194726ea4ad4e05372e03211ca68 SHA512 1339849966dd75beff966e438301c7b2421afe136f2b0c9c31bcb231418a0c1bc0bc6a00dda1eaa4cd5c47b240f77e03737a41b4408d67f6dbd7cdb8ce1cd6fb
 DIST cligen-1.5.32.tar.gz 427842 BLAKE2B ca950deeec655ae30e756c81e281ff31c3bae9cd39c31aae6a33042b91a2fe57332210483e13ad047403c9c065d79d8757f40d6b858b1f6b412666ef7c49351b SHA512 c8f2711d458443f1917c539354db04f22f4d0d0d9e8a7edecf7f798319d5ab64b11c82c840694e7a00e07ba960c39d26079e196c36574d7f37dea7125daa2dd6
+DIST cligen-1.5.33.tar.gz 429027 BLAKE2B 8dd797a175435a6dd43f04e86f0e882f745533b97572871fffb040c617a7457cee43d3dda53591823c82dcec42aca396d7831d5e309c87923281529b7c41c1c0 SHA512 6a29bd6b2448161b5d76d96b2d1c3b330b84ab7d1863b4e0b6982939c89da86e251f7df7606ef9f73bdd1b1066fb9496f315b471407ffe0d73b56f73da9ea62e

diff --git a/dev-nim/cligen/cligen-1.5.30.ebuild b/dev-nim/cligen/cligen-1.5.33.ebuild
similarity index 100%
rename from dev-nim/cligen/cligen-1.5.30.ebuild
rename to dev-nim/cligen/cligen-1.5.33.ebuild


             reply	other threads:[~2022-12-25  2:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25  2:19 Anna Vyalkova [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-01  2:10 [gentoo-commits] repo/proj/guru:dev commit in: dev-nim/cligen/ Anna Vyalkova
2023-07-09  2:00 Anna Vyalkova
2023-06-30 16:28 Anna Vyalkova
2023-05-28 12:14 Anna Vyalkova
2023-05-20  8:17 Anna Vyalkova
2023-05-08 16:45 Anna Vyalkova
2023-04-26 14:29 Anna Vyalkova
2023-03-22 18:58 Anna Vyalkova
2023-03-20  6:00 Anna Vyalkova
2023-03-07 15:33 Anna Vyalkova
2023-03-01  2:33 Anna Vyalkova
2023-02-25 23:27 Anna Vyalkova
2023-01-26 20:53 Anna Vyalkova
2023-01-17 14:27 Anna Vyalkova
2023-01-05 13:08 Anna Vyalkova
2022-11-26 13:51 Anna Vyalkova
2022-10-20 21:50 Anna Vyalkova
2022-10-10 16:43 Anna Vyalkova
2022-08-04 18:25 Anna Vyalkova
2022-08-04 13:10 Anna Vyalkova
2022-07-11  6:42 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=1671934760.e57a5ad8d87d97e9520034576dbf232f07584111.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