From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-block/io-scheduler-udev-rules/
Date: Wed, 5 Jul 2023 18:27:29 +0000 (UTC) [thread overview]
Message-ID: <1688581633.dc416b85d2c2aec4a1fa44d038a51be9b2c25b91.sam@gentoo> (raw)
commit: dc416b85d2c2aec4a1fa44d038a51be9b2c25b91
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 5 17:45:38 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jul 5 18:27:13 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dc416b85
sys-block/io-scheduler-udev-rules: add gitlab upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-block/io-scheduler-udev-rules/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sys-block/io-scheduler-udev-rules/metadata.xml b/sys-block/io-scheduler-udev-rules/metadata.xml
index 572c7daf2ccf..787423c1b6a1 100644
--- a/sys-block/io-scheduler-udev-rules/metadata.xml
+++ b/sys-block/io-scheduler-udev-rules/metadata.xml
@@ -4,4 +4,7 @@
<maintainer type="person">
<email>pacho@gentoo.org</email>
</maintainer>
+ <upstream>
+ <remote-id type="gitlab">pachoramos/io-scheduler-udev-rules</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2023-07-05 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 18:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 9:14 [gentoo-commits] repo/gentoo:master commit in: sys-block/io-scheduler-udev-rules/ Arthur Zamarin
2024-08-12 9:07 Pacho Ramos
2023-07-05 18:27 Sam James
2023-04-25 19:01 Sam James
2022-06-18 10:42 Pacho Ramos
2022-06-18 10:42 Pacho Ramos
2021-12-02 18:06 Pacho Ramos
2021-11-06 8:53 Pacho Ramos
2019-04-25 16:35 Pacho Ramos
2019-04-14 14:16 Pacho Ramos
2019-04-14 14:16 Pacho Ramos
2019-04-09 17:16 Pacho Ramos
2019-04-08 21:26 Pacho Ramos
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=1688581633.dc416b85d2c2aec4a1fa44d038a51be9b2c25b91.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