From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/seatd/
Date: Sun, 14 Aug 2022 20:06:10 +0000 (UTC) [thread overview]
Message-ID: <1660506942.d1b6e8e188033a516b6bf9141f4bdc4359699c78.sam@gentoo> (raw)
commit: d1b6e8e188033a516b6bf9141f4bdc4359699c78
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 14 19:55:42 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Aug 14 19:55:42 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d1b6e8e1
sys-auth/seatd: add sourcehut upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-auth/seatd/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sys-auth/seatd/metadata.xml b/sys-auth/seatd/metadata.xml
index 827e2ce4f139..8ad208539426 100644
--- a/sys-auth/seatd/metadata.xml
+++ b/sys-auth/seatd/metadata.xml
@@ -17,4 +17,7 @@
<flag name="builtin">Enable embedded server in libseat</flag>
<flag name="server">Enable standalone seatd server</flag>
</use>
+ <upstream>
+ <remote-id type="sourcehut">~kennylevinsen/seatd</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2022-08-14 20:06 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 20:06 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 7:53 [gentoo-commits] repo/gentoo:master commit in: sys-auth/seatd/ Arthur Zamarin
2023-08-23 20:05 Arthur Zamarin
2023-08-23 20:05 Arthur Zamarin
2023-08-23 20:05 Arthur Zamarin
2023-08-23 20:05 Arthur Zamarin
2023-07-21 11:00 Arthur Zamarin
2023-07-21 11:00 Arthur Zamarin
2023-07-21 11:00 Arthur Zamarin
2023-05-31 8:37 Arthur Zamarin
2022-11-13 11:39 Sam James
2022-11-13 11:39 Sam James
2022-11-12 12:13 Arthur Zamarin
2022-11-12 12:13 Arthur Zamarin
2022-11-12 12:13 Arthur Zamarin
2022-09-28 21:27 Sam James
2022-09-28 19:05 Arthur Zamarin
2022-09-28 19:05 Arthur Zamarin
2022-09-28 16:29 Arthur Zamarin
2022-09-15 16:41 Arthur Zamarin
2022-09-15 16:41 Arthur Zamarin
2022-08-19 6:16 Arthur Zamarin
2022-08-19 5:19 Arthur Zamarin
2022-08-18 23:08 Sam James
2022-08-18 23:08 Sam James
2022-08-18 23:08 Sam James
2022-08-18 23:08 Sam James
2022-05-26 1:12 Sam James
2022-05-17 8:37 WANG Xuerui
2022-05-17 8:37 WANG Xuerui
2022-05-17 5:59 Sam James
2022-04-30 12:06 Arthur Zamarin
2022-04-30 12:00 Arthur Zamarin
2022-02-25 21:03 Arthur Zamarin
2022-02-25 18:27 Sam James
2022-02-25 17:56 Arthur Zamarin
2022-02-25 17:56 Arthur Zamarin
2022-02-25 15:46 Arthur Zamarin
2022-02-23 21:38 Arthur Zamarin
2022-02-05 17:01 James Le Cuirot
2021-12-07 2:17 Sam James
2021-12-06 11:31 Agostino Sarubbo
2021-12-06 7:08 Agostino Sarubbo
2021-10-23 13:00 Arthur Zamarin
2021-10-23 13:00 Arthur Zamarin
2021-10-23 13:00 Arthur Zamarin
2021-10-15 6:55 Arthur Zamarin
2021-09-17 1:52 Ionen Wolkens
2021-09-17 1:52 Ionen Wolkens
2021-09-13 9:58 Arthur Zamarin
2021-09-13 6:41 Arthur Zamarin
2021-09-13 6:41 Arthur Zamarin
2021-08-07 8:25 Ionen Wolkens
2021-08-07 8:25 Ionen Wolkens
2021-07-02 7:38 Joonas Niilola
2021-06-13 11:12 Sam James
2021-06-13 11:12 Sam James
2021-03-17 6:44 Joonas Niilola
2020-12-11 18:02 Matthew Thode
2020-12-11 7:58 Joonas Niilola
2020-11-13 20:53 Aaron Bauman
2020-11-11 17:24 Aaron Bauman
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=1660506942.d1b6e8e188033a516b6bf9141f4bdc4359699c78.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