From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-db/rqlite/
Date: Sun, 28 Jun 2020 20:51:27 +0000 (UTC) [thread overview]
Message-ID: <1593377473.7c0a94b4b62a486fd5e4cd9a156bd9ef7e59515f.bman@gentoo> (raw)
commit: 7c0a94b4b62a486fd5e4cd9a156bd9ef7e59515f
Author: Michael Mair-Keimberger <m.mairkeimberger <AT> gmail <DOT> com>
AuthorDate: Sun Jun 28 16:10:03 2020 +0000
Commit: Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Sun Jun 28 20:51:13 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7c0a94b4
dev-db/rqlite: use HTTPS
Package-Manager: Portage-2.3.103, Repoman-2.3.23
Signed-off-by: Michael Mair-Keimberger <m.mairkeimberger <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/16474
Signed-off-by: Aaron Bauman <bman <AT> gentoo.org>
dev-db/rqlite/rqlite-5.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-db/rqlite/rqlite-5.2.0.ebuild b/dev-db/rqlite/rqlite-5.2.0.ebuild
index b0f87c9c7b3..46bff9b3335 100644
--- a/dev-db/rqlite/rqlite-5.2.0.ebuild
+++ b/dev-db/rqlite/rqlite-5.2.0.ebuild
@@ -6,7 +6,7 @@ inherit go-module
EGIT_COMMIT=77863e5a13110f1fca87b6fce84a7169c3aa58f5
DESCRIPTION="Replicated SQLite using the Raft consensus protocol"
-HOMEPAGE="https://github.com/rqlite/rqlite http://www.philipotoole.com/tag/rqlite/"
+HOMEPAGE="https://github.com/rqlite/rqlite https://www.philipotoole.com/tag/rqlite/"
EGO_SUM=(
"github.com/Bowery/prompt v0.0.0-20190916142128-fa8279994f75"
next reply other threads:[~2020-06-28 20:51 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 20:51 Aaron Bauman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-29 2:21 [gentoo-commits] repo/gentoo:master commit in: dev-db/rqlite/ Zac Medico
2025-01-24 23:49 Zac Medico
2025-01-21 17:24 Zac Medico
2025-01-11 23:40 Zac Medico
2024-12-29 2:32 Zac Medico
2024-12-29 2:32 Zac Medico
2024-12-24 22:23 Zac Medico
2024-12-17 22:30 Zac Medico
2024-12-14 22:34 Zac Medico
2024-12-12 0:19 Zac Medico
2024-11-28 1:03 Zac Medico
2024-11-28 1:02 Zac Medico
2024-11-26 3:01 Zac Medico
2024-11-26 3:01 Zac Medico
2024-11-14 22:22 Zac Medico
2024-11-14 22:22 Zac Medico
2024-11-06 0:58 Zac Medico
2024-11-06 0:56 Zac Medico
2024-06-08 17:31 Zac Medico
2024-06-08 17:31 Zac Medico
2024-03-24 20:02 Zac Medico
2024-03-24 20:01 Zac Medico
2024-01-22 2:29 Zac Medico
2023-12-10 23:42 Zac Medico
2023-05-11 4:06 Zac Medico
2023-01-08 23:12 Zac Medico
2022-12-17 1:01 Zac Medico
2022-11-22 0:26 Zac Medico
2022-11-13 1:41 Zac Medico
2022-11-13 1:41 Zac Medico
2022-10-24 23:48 Zac Medico
2022-10-22 22:17 Zac Medico
2022-10-21 0:03 Zac Medico
2022-10-21 0:03 Zac Medico
2022-10-15 23:56 Zac Medico
2022-10-14 1:05 Zac Medico
2022-09-29 0:42 Zac Medico
2022-09-29 0:42 Zac Medico
2022-08-07 22:24 Zac Medico
2022-07-24 21:58 Zac Medico
2022-06-18 22:06 Zac Medico
2022-06-02 3:35 Zac Medico
2022-05-15 22:51 Zac Medico
2022-05-15 22:51 Zac Medico
2022-05-13 21:59 Zac Medico
2022-05-13 21:59 Zac Medico
2022-02-06 19:10 Zac Medico
2022-02-05 17:16 Zac Medico
2022-02-04 23:07 Zac Medico
2022-01-30 23:58 Zac Medico
2022-01-17 23:02 Zac Medico
2022-01-01 1:23 Zac Medico
2022-01-01 1:23 Zac Medico
2021-12-21 17:30 Zac Medico
2021-11-14 3:40 Zac Medico
2021-11-12 6:55 Zac Medico
2021-10-23 0:08 Zac Medico
2021-02-28 20:13 Zac Medico
2021-02-28 20:08 Zac Medico
2021-02-24 17:21 Zac Medico
2020-05-12 23:20 William Hubbs
2020-05-12 23:16 William Hubbs
2020-01-12 2:19 Zac Medico
2019-12-31 22:36 Zac Medico
2019-12-31 21:46 Zac Medico
2019-11-30 0:52 Zac Medico
2019-09-21 2:23 Zac Medico
2019-04-29 17:52 Zac Medico
2019-04-25 5:40 Zac Medico
2019-04-14 3:56 Zac Medico
2019-03-16 21:58 Zac Medico
2019-03-16 21:58 Zac Medico
2019-01-22 9:29 Zac Medico
2019-01-22 9:03 Zac Medico
2018-05-27 2:33 Zac Medico
2018-05-27 0:34 Zac Medico
2017-09-15 7:06 Zac Medico
2017-09-15 4:59 Zac Medico
2017-08-09 6:46 Zac Medico
2017-08-09 6:46 Zac Medico
2017-06-19 1:28 Zac Medico
2017-06-19 1:15 Zac Medico
2017-06-19 1:15 Zac Medico
2017-06-06 21:40 Zac Medico
2016-05-02 5:33 Zac Medico
2016-05-02 5:24 Zac Medico
2016-05-01 19:18 Zac Medico
2016-04-16 22:59 Zac Medico
2016-04-11 1:50 Zac Medico
2016-03-09 8:52 Zac Medico
2016-03-09 8:29 Zac Medico
2016-02-25 10:29 Zac Medico
2016-02-23 9:26 Zac Medico
2016-02-13 10:48 Zac Medico
2016-02-13 10:43 Zac Medico
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=1593377473.7c0a94b4b62a486fd5e4cd9a156bd9ef7e59515f.bman@gentoo \
--to=bman@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