public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/clang-toolchain-symlinks/
Date: Tue,  6 Dec 2022 06:18:42 +0000 (UTC)	[thread overview]
Message-ID: <1670306592.214d914ac3d4d831a373d9057bd33f7103580cd9.xen0n@gentoo> (raw)

commit:     214d914ac3d4d831a373d9057bd33f7103580cd9
Author:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Tue Dec  6 06:01:03 2022 +0000
Commit:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Tue Dec  6 06:03:12 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=214d914a

sys-devel/clang-toolchain-symlinks: drop PROPERTIES=live for 16-r2

It's only for silencing the "no KEYWORDS" warnings, now that we have
~loong on the ebuild it's about time to drop it because the ebuild
actually isn't pulling from VCS.

Suggested-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>

 sys-devel/clang-toolchain-symlinks/clang-toolchain-symlinks-16-r2.ebuild | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sys-devel/clang-toolchain-symlinks/clang-toolchain-symlinks-16-r2.ebuild b/sys-devel/clang-toolchain-symlinks/clang-toolchain-symlinks-16-r2.ebuild
index 693d17b7b00e..574b2739f3a0 100644
--- a/sys-devel/clang-toolchain-symlinks/clang-toolchain-symlinks-16-r2.ebuild
+++ b/sys-devel/clang-toolchain-symlinks/clang-toolchain-symlinks-16-r2.ebuild
@@ -13,7 +13,6 @@ S=${WORKDIR}
 LICENSE="public-domain"
 SLOT="${PV}"
 KEYWORDS="~loong"
-PROPERTIES="live"
 IUSE="gcc-symlinks multilib-symlinks +native-symlinks"
 
 # Blocker for bug #872416


             reply	other threads:[~2022-12-06  6:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  6:18 WANG Xuerui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-06 21:53 [gentoo-commits] repo/gentoo:master commit in: sys-devel/clang-toolchain-symlinks/ Sam James
2024-12-06 21:53 Sam James
2024-09-08 16:04 Arthur Zamarin
2024-07-23 14:11 Sam James
2024-07-23 14:07 Michał Górny
2024-07-23 13:58 Sam James
2024-07-23 13:58 Sam James
2024-07-23 13:36 Sam James
2024-07-23 13:36 Sam James
2024-07-23 12:25 Sam James
2024-03-23 16:23 Sam James
2024-03-23 16:23 Sam James
2024-03-23 16:23 Sam James
2024-03-06 17:03 Michał Górny
2024-01-28  8:57 Sam James
2024-01-24  6:33 Michał Górny
2024-01-13 11:30 Joonas Niilola
2024-01-12  9:24 Sam James
2023-12-22 16:43 Michał Górny
2023-10-19 15:13 Michał Górny
2023-09-19 19:47 Michał Górny
2023-08-26 20:00 Mike Gilbert
2023-08-02 16:11 Sam James
2023-08-02 16:11 Sam James
2023-08-02 16:11 Sam James
2023-07-25 16:11 Michał Górny
2023-07-14 15:52 Arthur Zamarin
2023-06-17 23:22 Sam James
2023-06-13 18:28 Arthur Zamarin
2023-03-18 15:03 Michał Górny
2023-01-25  8:12 Michał Górny
2022-11-27 12:55 WANG Xuerui
2022-11-20  0:23 Sam James
2022-11-05 11:33 Joonas Niilola
2022-11-02 13:50 Agostino Sarubbo
2022-10-29  7:22 Agostino Sarubbo
2022-10-26 19:21 Arthur Zamarin
2022-10-26 17:10 Arthur Zamarin
2022-10-25 10:15 Arthur Zamarin
2022-10-13 15:41 Michał Górny
2022-09-23 23:02 Sam James
2022-09-20 16:55 Michał Górny
2022-09-20 11:17 Michał Górny
2022-09-20 11:07 Michał Górny

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=1670306592.214d914ac3d4d831a373d9057bd33f7103580cd9.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