public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/graphql-core/
Date: Sun,  5 Jul 2020 11:51:57 +0000 (UTC)	[thread overview]
Message-ID: <1593947754.bdfa2c35820ddb3d30c3682288b32c0969b1ede1.andrewammerlaan@gentoo> (raw)
Message-ID: <20200705115157.sXP4Ozvo0SHe1NtyhL8jrV_FNZx4SgvcrbmyWKrNKeI@z> (raw)

commit:     bdfa2c35820ddb3d30c3682288b32c0969b1ede1
Author:     Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
AuthorDate: Sun Jul  5 11:15:54 2020 +0000
Commit:     Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Sun Jul  5 11:15:54 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=bdfa2c35

dev-python/graphql-core: version bump

Package-Manager: Portage-2.3.103, Repoman-2.3.23
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> riseup.net>

 dev-python/graphql-core/Manifest                                        | 2 +-
 .../{graphql-core-3.0.5.ebuild => graphql-core-3.1.1.ebuild}            | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/graphql-core/Manifest b/dev-python/graphql-core/Manifest
index 3b42943..725f60e 100644
--- a/dev-python/graphql-core/Manifest
+++ b/dev-python/graphql-core/Manifest
@@ -1 +1 @@
-DIST graphql-core-3.0.5.tar.gz 462955 BLAKE2B 21d2b814ea4d2e330c6f936f4f7a34e84de43b327bd40f7e5c94c677cfdfb2db03c27c18fc4cd5d9a4eca0330f3a306efe1942bf08e96923d9444c5976960a86 SHA512 89ee9c2b039f3aa50ee032a679f2145480d63ec8aad3ac02273c301949740fb44f4b406ed5116b5466bb870997012416f0ea1367bdb2de5f82407168b1995a8b
+DIST graphql-core-3.1.1.tar.gz 481087 BLAKE2B e7bf05f4da9aa1c37acf802b830c05427a3f10fd36a716f194bb21ba3812ae5322534c67b692135a901f23dd48d46fe404a46b2b90cc7ee3862241a6381fd405 SHA512 62bef44d7d73eff1f1dc05e169fd765d4ea4d9716bbde26bc20ee826eb4fa78bb41deed1a196c37a24d4c5aa7e7965de86bee441c4a53f0b18f0cb2364d4cdec

diff --git a/dev-python/graphql-core/graphql-core-3.0.5.ebuild b/dev-python/graphql-core/graphql-core-3.1.1.ebuild
similarity index 100%
rename from dev-python/graphql-core/graphql-core-3.0.5.ebuild
rename to dev-python/graphql-core/graphql-core-3.1.1.ebuild


             reply	other threads:[~2020-07-05 11:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 11:37 Andrew Ammerlaan [this message]
2020-07-05 11:51 ` [gentoo-commits] repo/proj/guru:master commit in: dev-python/graphql-core/ Andrew Ammerlaan
  -- strict thread matches above, loose matches on Subject: below --
2024-04-13 22:19 Julien Roy
2024-04-13 21:31 ` [gentoo-commits] repo/proj/guru:dev " Julien Roy
2023-04-29 11:41 Anna Vyalkova
2023-04-29  6:23 Anna Vyalkova
2023-04-28  7:06 Anna Vyalkova
2023-03-17 13:32 Anna Vyalkova
2022-06-05 20:58 Alessandro Barbieri
2022-06-01  5:03 Anna Vyalkova
2021-12-14  7:14 Anna Vyalkova
2021-10-09  8:48 Theo Anderson
2021-05-26  1:57 Anna Vyalkova
2021-04-28  2:16 Theo Anderson
2021-04-28  2:16 Theo Anderson
2021-02-15 11:57 Theo Anderson
2021-02-15 11:57 Theo Anderson
2020-12-09  4:41 Theo Anderson
2020-09-24 12:17 Andrew Ammerlaan
2020-07-05 10:58 Andrew Ammerlaan

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=1593947754.bdfa2c35820ddb3d30c3682288b32c0969b1ede1.andrewammerlaan@gentoo \
    --to=andrewammerlaan@riseup.net \
    --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