From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-dialup/rp-pppoe/
Date: Tue, 6 Sep 2022 21:52:08 +0000 (UTC) [thread overview]
Message-ID: <1662501107.8ae73c3cf0f5c271a6ae8c2a40d42274bd0c54eb.sam@gentoo> (raw)
commit: 8ae73c3cf0f5c271a6ae8c2a40d42274bd0c54eb
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 6 21:51:47 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Sep 6 21:51:47 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8ae73c3c
net-dialup/rp-pppoe: Stabilize 3.15-r2 sparc, #868906
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-dialup/rp-pppoe/rp-pppoe-3.15-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-dialup/rp-pppoe/rp-pppoe-3.15-r2.ebuild b/net-dialup/rp-pppoe/rp-pppoe-3.15-r2.ebuild
index 54631024c318..63d63b21787b 100644
--- a/net-dialup/rp-pppoe/rp-pppoe-3.15-r2.ebuild
+++ b/net-dialup/rp-pppoe/rp-pppoe-3.15-r2.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://dianne.skoll.ca/projects/rp-pppoe/download/${P}.tar.gz
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~sparc x86"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv sparc x86"
IUSE="tk"
RDEPEND="
next reply other threads:[~2022-09-06 21:52 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 21:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-10 5:54 [gentoo-commits] repo/gentoo:master commit in: net-dialup/rp-pppoe/ Sam James
2023-05-30 16:51 Arthur Zamarin
2023-05-28 11:55 Sam James
2023-05-28 11:36 Sam James
2023-05-28 11:36 Sam James
2023-05-28 7:11 Joonas Niilola
2023-05-28 7:11 Joonas Niilola
2023-05-13 6:02 Sam James
2023-05-13 3:31 Sam James
2023-05-10 19:39 Sam James
2023-05-10 19:39 Sam James
2023-05-10 19:39 Sam James
2023-04-23 4:56 Sam James
2022-12-24 7:42 Sam James
2022-12-24 7:42 Sam James
2022-10-28 20:09 Sam James
2022-09-16 18:36 Arthur Zamarin
2022-09-15 16:57 Arthur Zamarin
2022-09-07 19:32 Mike Gilbert
2022-09-07 1:50 Sam James
2022-09-06 21:37 Sam James
2022-09-06 21:35 Sam James
2022-09-06 21:15 Sam James
2022-05-26 5:06 WANG Xuerui
2022-04-21 19:35 Jakov Smolić
2022-01-19 11:35 Lars Wendler
2021-12-06 15:20 Sam James
2021-12-06 1:17 Sam James
2021-12-06 0:10 Sam James
2021-12-05 18:31 Sam James
2021-12-05 3:45 Sam James
2021-12-01 21:29 Sam James
2021-05-20 14:59 Lars Wendler
2021-05-20 14:58 Lars Wendler
2021-05-06 9:57 Sam James
2021-05-05 16:09 Sergei Trofimovich
2021-05-04 22:25 Sam James
2021-05-04 7:01 Agostino Sarubbo
2021-04-16 10:25 David Seifert
2020-07-03 7:38 Lars Wendler
2018-08-26 17:08 Michał Górny
2017-11-09 22:05 Mike Gilbert
2017-04-18 6:47 Jeroen Roovers
2017-02-05 16:49 Markus Meier
2016-12-19 14:25 Aaron Bauman
2016-12-14 9:14 Tobias Klausmann
2016-07-19 12:07 Lars Wendler
2016-01-22 8:28 Michael Palimaka
2016-01-17 21:07 Lars Wendler
2015-12-27 9:43 Mikle Kolyada
2015-12-07 11:40 Agostino Sarubbo
2015-11-26 19:28 Markus Meier
2015-11-23 9:25 Agostino Sarubbo
2015-11-18 10:11 Jeroen Roovers
2015-11-18 8:57 Agostino Sarubbo
2015-11-18 6:47 Jeroen Roovers
2015-11-16 16:53 Agostino Sarubbo
2015-11-13 21:38 Lars Wendler
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=1662501107.8ae73c3cf0f5c271a6ae8c2a40d42274bd0c54eb.sam@gentoo \
--to=sam@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