public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Takuya Wakazono" <pastalian46@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: net-client/telescope/
Date: Sun, 30 Jun 2024 13:50:03 +0000 (UTC)	[thread overview]
Message-ID: <1719755174.3c781542f05b94295664ab20fab8301e64f75607.pastalian46@gentoo> (raw)

commit:     3c781542f05b94295664ab20fab8301e64f75607
Author:     Takuya Wakazono <pastalian46 <AT> gmail <DOT> com>
AuthorDate: Sun Jun 30 13:46:14 2024 +0000
Commit:     Takuya Wakazono <pastalian46 <AT> gmail <DOT> com>
CommitDate: Sun Jun 30 13:46:14 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=3c781542

net-client/telescope: update HOMEPAGE

Signed-off-by: Takuya Wakazono <pastalian46 <AT> gmail.com>

 net-client/telescope/metadata.xml            | 4 ++--
 net-client/telescope/telescope-0.10.1.ebuild | 2 +-
 net-client/telescope/telescope-0.9.ebuild    | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/net-client/telescope/metadata.xml b/net-client/telescope/metadata.xml
index 6d6c168bd..cdea2d6cb 100644
--- a/net-client/telescope/metadata.xml
+++ b/net-client/telescope/metadata.xml
@@ -7,7 +7,7 @@
 		<name>Omar Polo</name>
 		<email>telescope@omarpolo.com</email>
 	</maintainer>
-	<doc>https://telescope.omarpolo.com/telescope.1.html</doc>
-	<remote-id type="github">omar-polo/telescope</remote-id>
+	<doc>https://www.telescope-browser.org/telescope.1.html</doc>
+	<remote-id type="github">telescope-browser/telescope</remote-id>
 </upstream>
 </pkgmetadata>

diff --git a/net-client/telescope/telescope-0.10.1.ebuild b/net-client/telescope/telescope-0.10.1.ebuild
index 1b1f3e9b5..a029f1a43 100644
--- a/net-client/telescope/telescope-0.10.1.ebuild
+++ b/net-client/telescope/telescope-0.10.1.ebuild
@@ -7,7 +7,7 @@ VERIFY_SIG_METHOD="signify"
 inherit optfeature toolchain-funcs verify-sig
 
 DESCRIPTION="w3m-like browser for Gemini"
-HOMEPAGE="https://telescope.omarpolo.com"
+HOMEPAGE="https://www.telescope-browser.org/"
 SRC_URI="https://ftp.omarpolo.com/${P}.tar.gz
 	verify-sig? ( https://ftp.omarpolo.com/${P}.tar.gz.sha256.sig )"
 

diff --git a/net-client/telescope/telescope-0.9.ebuild b/net-client/telescope/telescope-0.9.ebuild
index 33d209019..2dbe0f17b 100644
--- a/net-client/telescope/telescope-0.9.ebuild
+++ b/net-client/telescope/telescope-0.9.ebuild
@@ -7,7 +7,7 @@ VERIFY_SIG_METHOD="signify"
 inherit toolchain-funcs verify-sig
 
 DESCRIPTION="w3m-like browser for Gemini"
-HOMEPAGE="https://telescope.omarpolo.com"
+HOMEPAGE="https://www.telescope-browser.org/"
 SRC_URI="https://ftp.omarpolo.com/${P}.tar.gz
 	verify-sig? ( https://ftp.omarpolo.com/${P}.tar.gz.sha256.sig )"
 


             reply	other threads:[~2024-06-30 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30 13:50 Takuya Wakazono [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-07  0:31 [gentoo-commits] repo/proj/guru:dev commit in: net-client/telescope/ Anna Vyalkova
2024-06-30  4:10 Anna Vyalkova
2024-04-09  1:24 Anna Vyalkova
2023-11-20  3:50 Anna Vyalkova
2022-05-30 17:47 Anna Vyalkova
2022-05-30 17:47 Anna Vyalkova
2022-01-16 17:58 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=1719755174.3c781542f05b94295664ab20fab8301e64f75607.pastalian46@gentoo \
    --to=pastalian46@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