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: Mon, 20 Mar 2023 06:00:58 +0000 (UTC)	[thread overview]
Message-ID: <1679250029.1cc2742c7e83351d2e932f02e0e8957df340030d.cybertailor@gentoo> (raw)

commit:     1cc2742c7e83351d2e932f02e0e8957df340030d
Author:     Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Sun Mar 19 18:20:29 2023 +0000
Commit:     Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Sun Mar 19 18:20:29 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=1cc2742c

dev-nim/cligen: add 1.5.42, drop 1.5.40

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

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

diff --git a/dev-nim/cligen/Manifest b/dev-nim/cligen/Manifest
index b6d158c98..44515baf3 100644
--- a/dev-nim/cligen/Manifest
+++ b/dev-nim/cligen/Manifest
@@ -1,2 +1,2 @@
-DIST cligen-1.5.40.tar.gz 436607 BLAKE2B 0d00712eac7a5797651f15e81082578aa0a6d3749bbd3baac4d11a5d91f43ba479ba3614fe1cd34257ab0006d3d04b5027d81ad16017d8b882f75f5d1d8631f7 SHA512 55424701ae4e52388bb4eb08e481fa7e3182ac20174b6b61b5c4ec3d05afef62616d78dc544810acef4cc3e73b0ba2fc986427aad00096120f6e517b13ad16a9
 DIST cligen-1.5.41.tar.gz 436734 BLAKE2B df5483d7b8f8026ecf7995ca2ea3547c7cead69b34b7d055d04696b75ab47a12e7fae54a438c0bcf227ef996b847cb040dfc5860172596c7aee3b06b2d12c01b SHA512 ad8a9557479d84741339b3a07c541bc4fb20bb46f91593b4d0c794103285521ccacd5c83b28cbd32c68ff5a1a8cf4902fa56724e433a23f00ec1a58d128a70dd
+DIST cligen-1.5.42.tar.gz 436756 BLAKE2B 37a65f79949308f2f372c55e4eca24be7c7ecb7638255f5381c597da00b3d4d6c206baabd104cbb26082ea7c456a1cf5c9defc9b949fd9770bf56ce365706e63 SHA512 ad596b2f2cacf4d1842fb3e3b445b4c5b1c4b2e179389e75755568e17a3c67f17bfa80046ecf07ea74415fd0b55de14a749630e3f766663ae1ac5503b0a666f7

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


             reply	other threads:[~2023-03-20  6:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  6:00 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-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-12-25  2:19 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=1679250029.1cc2742c7e83351d2e932f02e0e8957df340030d.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