From: "Piotr Karbowski" <slashbeast@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/mergerfs/
Date: Wed, 9 Aug 2023 18:14:29 +0000 (UTC) [thread overview]
Message-ID: <1691604863.0131861520d26ace8d26e9ba7a9f72192242ad8b.slashbeast@gentoo> (raw)
commit: 0131861520d26ace8d26e9ba7a9f72192242ad8b
Author: Piotr Karbowski <slashbeast <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 9 18:10:27 2023 +0000
Commit: Piotr Karbowski <slashbeast <AT> gentoo <DOT> org>
CommitDate: Wed Aug 9 18:14:23 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01318615
sys-fs/mergerfs: drop myself as maintainer; m-n.
Signed-off-by: Piotr Karbowski <slashbeast <AT> gentoo.org>
sys-fs/mergerfs/metadata.xml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/sys-fs/mergerfs/metadata.xml b/sys-fs/mergerfs/metadata.xml
index d63ca378bfc1..30388cdafb75 100644
--- a/sys-fs/mergerfs/metadata.xml
+++ b/sys-fs/mergerfs/metadata.xml
@@ -1,10 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>slashbeast@gentoo.org</email>
- <name>Piotr Karbowski</name>
- </maintainer>
+ <!-- maintainer-needed -->
<upstream>
<remote-id type="github">trapexit/mergerfs</remote-id>
</upstream>
next reply other threads:[~2023-08-09 18:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:14 Piotr Karbowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 2:55 [gentoo-commits] repo/gentoo:master commit in: sys-fs/mergerfs/ Sam James
2024-11-01 2:55 Sam James
2024-06-02 0:32 Sam James
2024-06-02 0:32 Sam James
2024-06-02 0:32 Sam James
2023-10-09 20:02 Sam James
2023-10-09 16:21 Arthur Zamarin
2023-07-23 16:40 Piotr Karbowski
2023-07-23 16:40 Piotr Karbowski
2023-05-21 13:49 Arthur Zamarin
2023-05-21 0:50 Sam James
2023-05-02 15:21 Arthur Zamarin
2023-05-02 15:21 Arthur Zamarin
2023-04-18 21:24 Piotr Karbowski
2023-03-29 20:51 Piotr Karbowski
2023-03-06 13:04 Arthur Zamarin
2023-03-06 12:52 Arthur Zamarin
2023-01-30 21:53 Piotr Karbowski
2023-01-30 21:53 Piotr Karbowski
2022-12-09 22:32 Sam James
2022-12-09 21:55 Arthur Zamarin
2022-10-13 21:45 Piotr Karbowski
2022-06-24 7:11 Agostino Sarubbo
2022-06-24 7:07 Agostino Sarubbo
2022-06-23 20:51 Piotr Karbowski
2022-03-27 23:20 Piotr Karbowski
2022-01-21 10:03 Jakov Smolić
2022-01-21 10:03 Jakov Smolić
2021-12-30 22:44 Piotr Karbowski
2021-12-30 22:44 Piotr Karbowski
2021-12-05 19:45 Piotr Karbowski
2021-08-19 21:10 Piotr Karbowski
2021-03-13 11:37 Sam James
2021-03-13 11:35 Sam James
2021-03-11 20:34 Piotr Karbowski
2021-02-09 23:34 Piotr Karbowski
2021-02-09 23:34 Piotr Karbowski
2021-02-04 14:42 Agostino Sarubbo
2021-02-04 14:09 Sam James
2021-02-03 22:06 Piotr Karbowski
2021-01-05 20:51 Sam James
2020-12-27 23:06 Sam James
2020-12-27 22:49 Piotr Karbowski
2020-12-10 22:23 Piotr Karbowski
2020-10-07 7:09 Agostino Sarubbo
2020-10-04 17:28 Piotr Karbowski
2020-03-08 10:37 Agostino Sarubbo
2020-03-07 20:59 Piotr Karbowski
2020-03-07 19:55 Piotr Karbowski
2019-12-10 9:54 Piotr Karbowski
2019-12-10 9:22 Piotr Karbowski
2019-12-09 20:01 Piotr Karbowski
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=1691604863.0131861520d26ace8d26e9ba7a9f72192242ad8b.slashbeast@gentoo \
--to=slashbeast@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