From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/sshfs/
Date: Tue, 13 Aug 2024 07:10:24 +0000 (UTC) [thread overview]
Message-ID: <1723530819.1e2af1678cceae83bb127359d5ca705b5b411e98.xen0n@gentoo> (raw)
commit: 1e2af1678cceae83bb127359d5ca705b5b411e98
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 7 06:05:28 2024 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Tue Aug 13 06:33:39 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1e2af167
net-fs/sshfs: keyword 3.7.3-r1 for ~loong
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
net-fs/sshfs/sshfs-3.7.3-r1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net-fs/sshfs/sshfs-3.7.3-r1.ebuild b/net-fs/sshfs/sshfs-3.7.3-r1.ebuild
index 1ed1ef7dd04b..62a830a7c66d 100644
--- a/net-fs/sshfs/sshfs-3.7.3-r1.ebuild
+++ b/net-fs/sshfs/sshfs-3.7.3-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -10,7 +10,7 @@ HOMEPAGE="https://github.com/libfuse/sshfs"
SRC_URI="https://github.com/libfuse/${PN}/releases/download/${P}/${P}.tar.xz"
LICENSE="GPL-2"
-KEYWORDS="amd64 arm arm64 ~hppa ~ia64 ppc ppc64 ~riscv ~sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 arm arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv ~sparc x86 ~amd64-linux ~x86-linux"
SLOT="0"
DEPEND=">=sys-fs/fuse-3.1.0:3
next reply other threads:[~2024-08-13 7:10 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 7:10 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-11 20:03 [gentoo-commits] repo/gentoo:master commit in: net-fs/sshfs/ Sam James
2022-10-01 6:19 Arthur Zamarin
2022-09-25 11:17 Yixun Lan
2022-09-25 4:43 Sam James
2022-09-25 1:18 Sam James
2022-09-25 1:18 Sam James
2022-09-24 15:04 Arthur Zamarin
2022-09-24 13:46 Arthur Zamarin
2022-09-24 13:46 Arthur Zamarin
2022-09-14 19:18 Arthur Zamarin
2022-08-22 23:54 Yixun Lan
2022-08-14 13:31 Yixun Lan
2022-08-14 13:31 Yixun Lan
2022-08-14 12:58 Yixun Lan
2021-10-27 4:13 Sam James
2021-10-26 3:16 Sam James
2021-10-26 3:16 Sam James
2021-10-26 3:14 Sam James
2021-10-26 3:12 Sam James
2021-10-26 3:12 Sam James
2020-12-24 4:28 Tim Harder
2020-07-27 13:54 Sam James
2020-05-07 3:51 Tim Harder
2020-04-28 18:11 Sergei Trofimovich
2020-04-27 6:43 Agostino Sarubbo
2020-04-27 6:43 Agostino Sarubbo
2020-04-26 15:29 Agostino Sarubbo
2020-04-26 14:19 Agostino Sarubbo
2020-04-26 14:16 Agostino Sarubbo
2020-01-18 1:47 Tim Harder
2019-11-19 0:39 Aaron Bauman
2019-11-18 21:19 Tim Harder
2019-11-18 21:19 Tim Harder
2019-10-17 15:04 Göktürk Yüksek
2019-05-10 20:33 Tim Harder
2018-12-22 18:48 Tim Harder
2018-12-12 4:13 Tim Harder
2018-11-19 7:24 Mikle Kolyada
2018-11-07 23:44 Thomas Deutschmann
2018-11-06 23:56 Sergei Trofimovich
2018-11-06 6:57 Mikle Kolyada
2018-06-13 2:23 Tim Harder
2018-03-31 18:50 Mart Raudsepp
2018-03-19 11:32 Tim Harder
2018-03-19 11:32 Tim Harder
2018-03-19 11:32 Tim Harder
2017-08-04 9:46 Tim Harder
2017-04-19 3:41 Tim Harder
2016-11-12 6:20 Tim Harder
2016-11-12 6:20 Tim Harder
2016-10-01 13:09 Jeroen Roovers
2016-10-01 7:54 Markus Meier
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=1723530819.1e2af1678cceae83bb127359d5ca705b5b411e98.xen0n@gentoo \
--to=xen0n@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