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: Fri, 30 Jun 2023 16:28:38 +0000 (UTC)	[thread overview]
Message-ID: <1688141563.74f130f5a37a932236995fc8a6c0c93ecc6ae408.cybertailor@gentoo> (raw)

commit:     74f130f5a37a932236995fc8a6c0c93ecc6ae408
Author:     Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Thu Jun 29 23:35:54 2023 +0000
Commit:     Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Fri Jun 30 16:12:43 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=74f130f5

dev-nim/cligen: add 1.6.7, drop 1.6.4

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

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

diff --git a/dev-nim/cligen/Manifest b/dev-nim/cligen/Manifest
index 7e596aae6..48603444f 100644
--- a/dev-nim/cligen/Manifest
+++ b/dev-nim/cligen/Manifest
@@ -1,2 +1,2 @@
-DIST cligen-1.6.4.tar.gz 441284 BLAKE2B df6652dc362af4f774606d94086e966598cfa961bbb4f16a511b53f4610600890871908bce6fcea6249511eb0c211bca57f10fdaf32b62a246d6937985f5166f SHA512 4b23c7c094ed51d5d2cc7143d84c970b68715fb29e43969a5372e46e7002c91d976796096c4f4a65dc4daf82474e1b4f6e701dafb3b473c1cf5bfa7956da0f63
 DIST cligen-1.6.6.tar.gz 441388 BLAKE2B ed15fe6d5b5a9a779ac8ed39c8b4f5fb4f44faa431bedcf8444c374f758d33a46b96b92ed785bc076431ea6bab45d3b2c2bff2d54590f2b9a66c648de18728aa SHA512 e09b760d825238b8719e2a1894123b604588e8375c7b337316fa9ec16d9022b8384cf2e8799f06010a41ec923d0c69fc93fff79d2a1c48673ffb6acb39d4d689
+DIST cligen-1.6.7.tar.gz 441610 BLAKE2B 46fda5067e6df440b9954a4b99e09454d7610c3ae4c878be533f097d7159d6eea9b3dd34bb63cab746e951818f15b901c53591ef51f78c39d9b784d25feb27ef SHA512 66026590c5ee319eac18ab1edbe39ad4858b206243ada3e64fbbfcad625eafa18adcb607a49ab225ca629b71ae28bf67c1e47360e08ea75e0d9df4f067fc67a2

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


             reply	other threads:[~2023-06-30 16:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 16:28 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-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-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=1688141563.74f130f5a37a932236995fc8a6c0c93ecc6ae408.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