From: "Viorel Munteanu" <ceamac@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-kernel/raspberrypi-sources/
Date: Fri, 12 Jul 2024 16:57:37 +0000 (UTC) [thread overview]
Message-ID: <1720803427.725e225159b72456f1efe3d4cf96b30001fff1ba.ceamac@gentoo> (raw)
commit: 725e225159b72456f1efe3d4cf96b30001fff1ba
Author: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 12 16:55:44 2024 +0000
Commit: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
CommitDate: Fri Jul 12 16:57:07 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=725e2251
sys-kernel/raspberrypi-sources: add myself as a maintainer
Signed-off-by: Viorel Munteanu <ceamac <AT> gentoo.org>
sys-kernel/raspberrypi-sources/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/sys-kernel/raspberrypi-sources/metadata.xml b/sys-kernel/raspberrypi-sources/metadata.xml
index 8a8dc9337af9..727d318f3e8d 100644
--- a/sys-kernel/raspberrypi-sources/metadata.xml
+++ b/sys-kernel/raspberrypi-sources/metadata.xml
@@ -5,6 +5,10 @@
<email>expeditioneer@gentoo.org</email>
<name>Dennis Lamm</name>
</maintainer>
+ <maintainer type="person">
+ <email>ceamac@gentoo.org</email>
+ <name>Viorel Munteanu</name>
+ </maintainer>
<upstream>
<bugs-to>https://github.com/raspberrypi/linux/issues</bugs-to>
<doc>https://www.raspberrypi.com/documentation/computers/linux_kernel.html</doc>
next reply other threads:[~2024-07-12 16:57 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 16:57 Viorel Munteanu [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-03 17:36 [gentoo-commits] repo/gentoo:master commit in: sys-kernel/raspberrypi-sources/ Viorel Munteanu
2024-09-03 17:22 Viorel Munteanu
2024-08-23 13:00 Arthur Zamarin
2024-08-13 16:08 Arthur Zamarin
2024-07-12 16:57 Viorel Munteanu
2024-04-20 3:20 Sam James
2023-12-30 3:04 Sam James
2023-12-30 3:04 Sam James
2023-06-07 16:39 Sam James
2023-03-24 14:14 Arthur Zamarin
2023-03-10 6:02 Dennis Lamm
2023-03-04 6:04 Arthur Zamarin
2023-03-04 5:47 Arthur Zamarin
2023-02-02 19:54 Dennis Lamm
2023-02-02 19:54 Dennis Lamm
2023-01-05 5:50 Dennis Lamm
2023-01-05 5:50 Dennis Lamm
2023-01-05 5:50 Dennis Lamm
2022-10-28 6:33 Dennis Lamm
2022-04-26 4:47 Dennis Lamm
2022-04-26 4:47 Dennis Lamm
2022-04-09 19:46 Arthur Zamarin
2022-04-09 19:36 Arthur Zamarin
2022-04-06 6:57 Dennis Lamm
2022-04-06 6:57 Dennis Lamm
2022-03-22 1:54 Sam James
2021-12-05 1:29 Sam James
2021-12-05 1:28 Sam James
2021-12-05 1:28 Sam James
2021-09-03 1:53 Sam James
2021-03-22 5:22 Sam James
2021-02-05 18:51 Sam James
2021-02-05 18:51 Sam James
2021-02-05 18:51 Sam James
2021-02-05 18:51 Sam James
2020-12-07 18:05 Sam James
2020-07-28 0:10 Sam James
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-01-11 8:29 Georgy Yakovlev
2018-01-04 17:43 Patrice Clement
2017-12-07 23:04 Steve Arnold
2017-12-07 20:38 Steve Arnold
2017-12-03 15:52 Patrice Clement
2017-10-01 5:44 Alexey Shvetsov
2017-07-12 22:36 Alexey Shvetsov
2017-03-07 7:28 Michael Weber
2017-03-07 7:04 Michael Weber
2016-02-11 8:11 Michael Weber
2016-02-11 7:21 Michael Weber
2015-11-28 13:01 Alfredo Tupone
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=1720803427.725e225159b72456f1efe3d4cf96b30001fff1ba.ceamac@gentoo \
--to=ceamac@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