From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-dialup/xl2tpd/
Date: Sun, 25 Jul 2021 03:58:50 +0000 (UTC) [thread overview]
Message-ID: <1627185523.68096270c9b14b9c9cf487c145e8da8c9e6c9e38.sam@gentoo> (raw)
commit: 68096270c9b14b9c9cf487c145e8da8c9e6c9e38
Author: Jaco Kroon <jaco <AT> uls <DOT> co <DOT> za>
AuthorDate: Fri Jul 23 07:13:06 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jul 25 03:58:43 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=68096270
net-dialup/xl2tpd: Adopt it.
Package-Manager: Portage-3.0.20, Repoman-3.0.2
Signed-off-by: Jaco Kroon <jaco <AT> uls.co.za>
Closes: https://github.com/gentoo/gentoo/pull/21753
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-dialup/xl2tpd/metadata.xml | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/net-dialup/xl2tpd/metadata.xml b/net-dialup/xl2tpd/metadata.xml
index bab6c029617..f45f6b9445d 100644
--- a/net-dialup/xl2tpd/metadata.xml
+++ b/net-dialup/xl2tpd/metadata.xml
@@ -1,7 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <!-- maintainer-needed -->
+ <maintainer type="person" proxied="yes">
+ <email>jaco@uls.co.za</email>
+ <name>Jaco Kroon</name>
+ </maintainer>
+ <maintainer type="project" proxied="proxy">
+ <email>proxy-maint@gentoo.org</email>
+ <name>Proxy Maintainers</name>
+ </maintainer>
<longdescription>xl2tpd is a fork of l2tpd Layer 2 Tunneling Protocol (L2TP) daemon that can be used to transfer frames of OSI layer 2 protocols through an IP tunnel. While it provides authentication via CHAP or PAP it does not provide encryption itself and should therefore be externally secured (via IPSEC).</longdescription>
<use>
<flag name="kernel">Enable kernel interface for PPPoL2TP</flag>
next reply other threads:[~2021-07-25 3:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 3:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-24 23:18 [gentoo-commits] repo/gentoo:master commit in: net-dialup/xl2tpd/ Sam James
2024-09-14 17:55 Arthur Zamarin
2024-09-14 17:55 Arthur Zamarin
2024-09-14 17:55 Arthur Zamarin
2024-09-14 17:55 Arthur Zamarin
2024-04-21 13:35 Michael Orlitzky
2024-04-19 11:43 Sam James
2024-04-18 22:54 Sam James
2024-04-18 20:07 Sam James
2024-04-18 20:07 Sam James
2022-12-21 10:11 Viorel Munteanu
2022-12-05 5:30 WANG Xuerui
2022-01-15 9:00 Ionen Wolkens
2021-07-24 23:02 Marek Szuba
2021-06-18 21:07 David Seifert
2021-04-20 6:39 Sergei Trofimovich
2021-04-19 4:31 Sam James
2021-04-18 21:27 Sam James
2021-04-18 21:20 Sam James
2021-03-16 20:16 Sam James
2021-03-16 19:57 Sam James
2021-03-07 11:58 David Seifert
2021-01-07 19:35 Sam James
2021-01-06 8:09 Sam James
2021-01-04 3:31 Sam James
2020-04-01 9:34 Piotr Karbowski
2020-02-02 0:09 Jonas Stein
2019-05-24 20:48 Aaron Bauman
2019-04-19 14:11 Michał Górny
2019-04-19 14:11 Michał Górny
2018-08-21 0:13 Sergei Trofimovich
2018-08-10 8:31 Michał Górny
2018-03-14 13:02 Mikle Kolyada
2018-03-11 2:16 Thomas Deutschmann
2018-03-10 22:55 Patrice Clement
2017-08-29 9:46 Patrice Clement
2017-08-13 13:28 Patrice Clement
2017-07-17 9:48 Alexis Ballier
2017-05-07 19:29 Mike Gilbert
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=1627185523.68096270c9b14b9c9cf487c145e8da8c9e6c9e38.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