public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-cpp/fbthrift/
Date: Sat, 16 Apr 2022 18:46:33 +0000 (UTC)	[thread overview]
Message-ID: <1650134781.79c9c188c06da48fa13f3f412c780fac30cfdfd5.Alessandro-Barbieri@gentoo> (raw)

commit:     79c9c188c06da48fa13f3f412c780fac30cfdfd5
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Sat Apr 16 18:46:21 2022 +0000
Commit:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Sat Apr 16 18:46:21 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=79c9c188

dev-cpp/fbthrift: add 2022.04.11.00, drop 2022.03.21.00

Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>

 dev-cpp/fbthrift/Manifest                                               | 2 +-
 .../{fbthrift-2022.03.21.00.ebuild => fbthrift-2022.04.11.00.ebuild}    | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-cpp/fbthrift/Manifest b/dev-cpp/fbthrift/Manifest
index ebe4d535f..bb9e7f8ea 100644
--- a/dev-cpp/fbthrift/Manifest
+++ b/dev-cpp/fbthrift/Manifest
@@ -1 +1 @@
-DIST fbthrift-2022.03.21.00.tar.gz 7178541 BLAKE2B 6e875f19ae19b5ccd1740d5eadb0b4f106d96b95ca1ced9e05a5bfd7f8e7de84aec722f0dfb0721c81e320185359d3f9c595ebfebef8638b6ca6788df98d37d4 SHA512 8d2d9430dc3a4ecc23042cd9bcf4eee888824449d05d98baec408aef806b934d643e578d3876169f69966c846aeddbe0aa84416c4e020cba028a49d2fccfe7ab
+DIST fbthrift-2022.04.11.00.tar.gz 7475837 BLAKE2B 27e035296d7c73562824a192f2bdc8789aa9ff674f9693e991b71b4543b417ad41aaf186681bdddbe494557fe0a3a4471751111e667e98348c763321e9343412 SHA512 e45088151e9de051e30b5ac34b07c35b965092ea0ad8075029fce57de5df44c908d0c30663ce35b455ad96f277d8935e08e3ecba331708b1835333cf90e87ce1

diff --git a/dev-cpp/fbthrift/fbthrift-2022.03.21.00.ebuild b/dev-cpp/fbthrift/fbthrift-2022.04.11.00.ebuild
similarity index 100%
rename from dev-cpp/fbthrift/fbthrift-2022.03.21.00.ebuild
rename to dev-cpp/fbthrift/fbthrift-2022.04.11.00.ebuild


             reply	other threads:[~2022-04-16 18:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 18:46 Alessandro Barbieri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15 16:06 [gentoo-commits] repo/proj/guru:master commit in: dev-cpp/fbthrift/ Julien Roy
2024-05-15 16:01 ` [gentoo-commits] repo/proj/guru:dev " Julien Roy
2023-02-28 12:58 Denis Reva
2022-05-31 15:36 Alessandro Barbieri
2022-05-28 12:53 Alessandro Barbieri
2022-04-01 14:41 Yuan Liao
2022-03-22 17:48 Alessandro Barbieri
2022-03-09  0:29 Alessandro Barbieri
2022-03-07  4:17 Alessandro Barbieri
2022-03-06  2:22 Alessandro Barbieri
2021-11-26 11:34 Denis Reva
2021-10-26 16:35 Alessandro Barbieri
2021-10-25 11:20 Alessandro Barbieri
2021-10-23 14:18 Alessandro Barbieri
2021-10-05 20:50 Alessandro Barbieri
2021-07-05  8:44 Alessandro Barbieri
2021-06-17 16:26 Alessandro Barbieri
2021-06-15 23:32 Alessandro Barbieri
2021-06-14  2:27 Alessandro Barbieri
2021-05-27 10:23 Alessandro Barbieri
2021-05-05  7:32 Alessandro Barbieri
2021-04-28 21:15 Alessandro Barbieri

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=1650134781.79c9c188c06da48fa13f3f412c780fac30cfdfd5.Alessandro-Barbieri@gentoo \
    --to=lssndrbarbieri@gmail.com \
    --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