public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gui-wm/hyprland/
Date: Sun, 12 Nov 2023 23:56:14 +0000 (UTC)	[thread overview]
Message-ID: <1699833170.f1514cca01b64af9f052153ecf20faa0f2cf0525.dlan@gentoo> (raw)

commit:     f1514cca01b64af9f052153ecf20faa0f2cf0525
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 12 23:52:50 2023 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sun Nov 12 23:52:50 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f1514cca

gui-wm/hyprland: forward keywords to live version

just keep it sync with normal version, to make sure
not to break the ebuild when doing copy & paste.

Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

 gui-wm/hyprland/hyprland-9999.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gui-wm/hyprland/hyprland-9999.ebuild b/gui-wm/hyprland/hyprland-9999.ebuild
index 6fed135cffd6..a63c7522ef43 100644
--- a/gui-wm/hyprland/hyprland-9999.ebuild
+++ b/gui-wm/hyprland/hyprland-9999.ebuild
@@ -15,7 +15,7 @@ else
 	SRC_URI="https://github.com/hyprwm/${PN^}/releases/download/v${PV}/source-v${PV}.tar.gz -> ${P}.gh.tar.gz"
 	S="${WORKDIR}/${PN}-source"
 
-	KEYWORDS="~amd64"
+	KEYWORDS="~amd64 ~riscv"
 fi
 
 LICENSE="BSD"


             reply	other threads:[~2023-11-12 23:56 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 23:56 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-26 12:49 [gentoo-commits] repo/gentoo:master commit in: gui-wm/hyprland/ Yixun Lan
2024-09-11  2:34 Yixun Lan
2024-09-11  2:34 Yixun Lan
2024-09-10 15:46 Jakov Smolić
2024-08-11  2:44 Yixun Lan
2024-08-11  2:44 Yixun Lan
2024-08-11  2:44 Yixun Lan
2024-08-11  2:44 Yixun Lan
2024-08-09  3:18 Yixun Lan
2024-08-09  3:18 Yixun Lan
2024-08-09  3:18 Yixun Lan
2024-08-09  3:18 Yixun Lan
2024-08-09  3:18 Yixun Lan
2024-07-27 17:16 Arthur Zamarin
2024-07-25  0:06 Yixun Lan
2024-07-01 22:40 Yixun Lan
2024-07-01 22:40 Yixun Lan
2024-06-30 15:05 James Le Cuirot
2024-06-25  8:18 Yixun Lan
2024-05-28 14:08 Yixun Lan
2024-05-23 16:10 Matt Turner
2024-05-15  8:04 Yixun Lan
2024-05-15  8:04 Yixun Lan
2024-05-13 18:00 Arthur Zamarin
2024-05-06  2:21 Yixun Lan
2024-04-27 11:09 Yixun Lan
2024-04-16 22:09 Yixun Lan
2024-04-16 22:09 Yixun Lan
2024-04-16 22:09 Yixun Lan
2024-04-15 23:51 Yixun Lan
2024-04-15 23:51 Yixun Lan
2024-04-13  5:45 Joonas Niilola
2024-04-08 12:56 Yixun Lan
2024-04-02 11:44 Yixun Lan
2024-03-17  9:10 Yixun Lan
2024-03-16 23:51 Yixun Lan
2024-03-16 23:51 Yixun Lan
2024-03-02  1:23 Yixun Lan
2024-03-01  1:08 Yixun Lan
2024-03-01  1:08 Yixun Lan
2024-02-23  0:50 Yixun Lan
2024-02-23  0:50 Yixun Lan
2024-02-23  0:50 Yixun Lan
2024-02-18  8:57 Yixun Lan
2024-02-18  8:57 Yixun Lan
2024-02-18  0:15 Sam James
2024-01-05 19:42 Jakov Smolić
2024-01-05 10:36 Sam James
2024-01-03 13:45 Yixun Lan
2024-01-03 13:45 Yixun Lan
2024-01-03 13:45 Yixun Lan
2023-12-20 15:19 Sam James
2023-12-13 12:27 Yixun Lan
2023-12-12  8:14 Yixun Lan
2023-12-12  8:14 Yixun Lan
2023-11-26  7:49 Yixun Lan
2023-11-26  7:49 Yixun Lan
2023-11-12 23:29 Yixun Lan
2023-11-12 23:29 Yixun Lan
2023-11-12  6:39 Sam James
2023-11-12  0:02 Yixun Lan
2023-11-11 11:23 Yixun Lan
2023-11-11 10:28 Yixun Lan
2023-11-11 10:28 Yixun Lan
2023-11-04 19:48 Sam James
2023-11-04 19:48 Sam James
2023-10-27  3:20 Sam James
2023-10-01  7:47 Sam James
2023-10-01  7:47 Sam James
2023-09-18  9:50 Sam James
2023-09-18  9:50 Sam James
2023-07-27  3:10 Sam James
2023-07-23  1:52 Sam James
2023-07-19 15:10 Sam James
2023-07-19 15:10 Sam James
2023-06-11  8:22 Joonas Niilola
2023-06-05  8:05 Sam James
2023-06-05  5:32 Sam James
2023-06-05  5:15 Sam James
2023-05-29 14:21 Sam James

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=1699833170.f1514cca01b64af9f052153ecf20faa0f2cf0525.dlan@gentoo \
    --to=dlan@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