public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/tree/
Date: Sun, 31 Jul 2022 11:09:04 +0000 (UTC)	[thread overview]
Message-ID: <1659265730.e30d67da7b6091754e9ce52dfc33e7d183fb9890.ago@gentoo> (raw)

commit:     e30d67da7b6091754e9ce52dfc33e7d183fb9890
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 31 11:08:50 2022 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Jul 31 11:08:50 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e30d67da

app-text/tree: ppc stable wrt bug #862369

Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 app-text/tree/tree-2.0.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-text/tree/tree-2.0.1.ebuild b/app-text/tree/tree-2.0.1.ebuild
index 7a3cf488cf83..d449fd9612b9 100644
--- a/app-text/tree/tree-2.0.1.ebuild
+++ b/app-text/tree/tree-2.0.1.ebuild
@@ -10,7 +10,7 @@ SRC_URI="ftp://mama.indstate.edu/linux/tree/${P}.tgz"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~x64-macos"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~m68k ~mips ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~x64-macos"
 IUSE=""
 
 RDEPEND=""


             reply	other threads:[~2022-07-31 11:09 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 11:09 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-08 11:07 [gentoo-commits] repo/gentoo:master commit in: app-text/tree/ Arthur Zamarin
2024-06-08 11:06 Arthur Zamarin
2024-06-07 13:35 Arthur Zamarin
2024-06-07 13:35 Arthur Zamarin
2024-06-06 17:30 Arthur Zamarin
2024-06-06 17:30 Arthur Zamarin
2024-06-06 17:30 Arthur Zamarin
2024-06-06 17:30 Arthur Zamarin
2024-06-06 17:30 Arthur Zamarin
2024-05-03 12:36 Sam James
2023-10-27 12:17 Sam James
2023-10-26 16:17 Arthur Zamarin
2023-10-26 13:04 Sam James
2023-10-26 13:04 Sam James
2023-10-26 12:49 Sam James
2023-10-26 12:49 Sam James
2023-10-26 12:49 Sam James
2023-10-26 12:49 Sam James
2023-09-01  4:02 Jonas Stein
2023-09-01  3:58 Jonas Stein
2023-05-05  9:52 Arthur Zamarin
2023-05-05  9:40 Arthur Zamarin
2023-05-05  6:31 Arthur Zamarin
2023-05-04 23:32 Sam James
2023-05-04 23:32 Sam James
2023-05-04 18:45 Arthur Zamarin
2023-05-04 18:39 Arthur Zamarin
2023-05-04 18:34 Arthur Zamarin
2023-05-01  5:20 Ulrich Müller
2023-05-01  5:20 Ulrich Müller
2023-04-27 13:58 Fabian Groffen
2023-04-27 13:58 Fabian Groffen
2023-01-13 18:45 Fabian Groffen
2023-01-04  2:11 Jonas Stein
2022-12-05 18:59 Jonas Stein
2022-12-02 18:59 Arthur Zamarin
2022-12-02  1:06 Sam James
2022-12-02  0:46 Sam James
2022-12-02  0:46 Sam James
2022-12-02  0:46 Sam James
2022-12-02  0:46 Sam James
2022-12-01 22:28 Jakov Smolić
2022-12-01 22:24 Jakov Smolić
2022-11-01  0:23 Jonas Stein
2022-11-01  0:23 Jonas Stein
2022-07-31 17:12 Arthur Zamarin
2022-07-31 11:11 Agostino Sarubbo
2022-07-31 11:10 Agostino Sarubbo
2022-07-31 11:08 Agostino Sarubbo
2022-07-31 11:06 Agostino Sarubbo
2022-07-30 21:19 Sam James
2022-07-30 21:19 Sam James
2022-07-30 19:37 Jonas Stein
2022-02-04 20:00 Jonas Stein
2021-08-19 11:22 Sam James
2021-01-06 13:46 Fabian Groffen
2020-12-23 22:57 Sam James
2020-12-21  9:36 Sergei Trofimovich
2020-11-27  8:07 Agostino Sarubbo
2020-11-27  7:55 Agostino Sarubbo
2020-04-14 15:52 Agostino Sarubbo
2020-04-14 13:02 Agostino Sarubbo
2020-04-14 13:01 Agostino Sarubbo
2020-04-14 13:01 Agostino Sarubbo
2020-04-14 10:12 Mart Raudsepp
2020-04-14  7:58 Agostino Sarubbo
2019-06-28 18:19 Jonas Stein
2019-05-05 10:29 Mikle Kolyada
2018-01-12  4:10 Mike Frysinger
2017-11-20 20:36 Jonas Stein
2017-11-20 17:24 Jonas Stein

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=1659265730.e30d67da7b6091754e9ce52dfc33e7d183fb9890.ago@gentoo \
    --to=ago@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