public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Viorel Munteanu" <ceamac@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/stone/
Date: Wed, 15 May 2024 05:19:49 +0000 (UTC)	[thread overview]
Message-ID: <1715750380.6bc58c4e6866d751a3f4c0366c057c76a2b73330.ceamac@gentoo> (raw)

commit:     6bc58c4e6866d751a3f4c0366c057c76a2b73330
Author:     Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
AuthorDate: Wed May 15 04:42:20 2024 +0000
Commit:     Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
CommitDate: Wed May 15 05:19:40 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6bc58c4e

dev-python/stone: add 3.3.6, drop 3.3.5

Signed-off-by: Viorel Munteanu <ceamac <AT> gentoo.org>

 dev-python/stone/Manifest                                   | 2 +-
 dev-python/stone/{stone-3.3.5.ebuild => stone-3.3.6.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/stone/Manifest b/dev-python/stone/Manifest
index 36cafb5472..7c1b0983e9 100644
--- a/dev-python/stone/Manifest
+++ b/dev-python/stone/Manifest
@@ -1 +1 @@
-DIST stone-3.3.5.gh.tar.gz 281069 BLAKE2B 659048ef899c0a40d466d2c7cafca69ddbfea79f0efa1a95d153dec1a7382903c706d97e7ee71346235fd2d69e8121ef5c822f97cbadefd92eb349e40644fc84 SHA512 28431dabec6f5698b40b7f759a56a330b38266ce9824132d46cda1d2453199f44913469e3ae3b13e466f8023d154a896bc75affd67aa9a385de9b6df8cf99afa
+DIST stone-3.3.6.gh.tar.gz 281082 BLAKE2B 5c2d19e98ad6f14b63a63e54a993820e8d31004d2e7fefcba4498c5315e3ec83548565cc575523e95801806add4185f0c14dc08c75d76cf4b44ba41e7e853463 SHA512 9a136f6b532390e7cc35880ebbc49a341b6730ebd9c27a2d1ea6d6bef62e09f79ac7bb41e66f26fec5debee4145ebb27b23a06c1087b3fd2dacde025c3710b7a

diff --git a/dev-python/stone/stone-3.3.5.ebuild b/dev-python/stone/stone-3.3.6.ebuild
similarity index 100%
rename from dev-python/stone/stone-3.3.5.ebuild
rename to dev-python/stone/stone-3.3.6.ebuild


             reply	other threads:[~2024-05-15  5:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  5:19 Viorel Munteanu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-20  7:23 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/stone/ Viorel Munteanu
2024-07-20  7:23 Viorel Munteanu
2024-07-17  4:13 Viorel Munteanu
2024-07-17  4:13 Viorel Munteanu
2024-05-14  5:15 [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2024-05-14  5:14 ` [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2024-05-14  5:15 [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2024-05-14  5:14 ` [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2024-05-10  6:27 Viorel Munteanu
2024-03-28 17:52 Viorel Munteanu
2024-03-28  6:23 Viorel Munteanu
2023-03-13  8:02 Viorel Munteanu
2023-03-12  9:14 [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
2023-03-12  9:08 ` [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2022-11-02 16:23 Viorel Munteanu
2022-01-27 13:42 Viorel Munteanu
2022-01-27 13:42 Viorel Munteanu
2022-01-09 11:32 Viorel Munteanu
2022-01-04  9:15 Viorel Munteanu
2021-12-29 12:07 Viorel Munteanu
2021-12-24 18:03 Viorel Munteanu

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=1715750380.6bc58c4e6866d751a3f4c0366c057c76a2b73330.ceamac@gentoo \
    --to=ceamac@gentoo.org \
    --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