From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/gcr/
Date: Sat, 29 Oct 2022 22:33:55 +0000 (UTC) [thread overview]
Message-ID: <1667082747.b84e9801399f94be495b709d97e9bfecfb082bad.mattst88@gentoo> (raw)
commit: b84e9801399f94be495b709d97e9bfecfb082bad
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 29 21:19:33 2022 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sat Oct 29 22:32:27 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b84e9801
app-crypt/gcr: Set remote-id
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
app-crypt/gcr/metadata.xml | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/app-crypt/gcr/metadata.xml b/app-crypt/gcr/metadata.xml
index 7b343b06be8a..11816fc8230a 100644
--- a/app-crypt/gcr/metadata.xml
+++ b/app-crypt/gcr/metadata.xml
@@ -1,8 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
-<maintainer type="project">
- <email>gnome@gentoo.org</email>
- <name>Gentoo GNOME Desktop</name>
-</maintainer>
+ <maintainer type="project">
+ <email>gnome@gentoo.org</email>
+ <name>Gentoo GNOME Desktop</name>
+ </maintainer>
+ <upstream>
+ <remote-id type="gnome-gitlab">GNOME/gcr</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2022-10-29 22:34 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 22:33 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-07 16:08 [gentoo-commits] repo/gentoo:master commit in: app-crypt/gcr/ Sam James
2025-01-16 16:55 Pacho Ramos
2024-06-06 0:45 Sam James
2024-06-06 0:45 Sam James
2024-06-06 0:45 Sam James
2024-05-06 7:09 Mart Raudsepp
2024-04-28 19:11 Ionen Wolkens
2024-04-07 6:51 Arthur Zamarin
2024-03-03 20:55 Mart Raudsepp
2023-05-02 19:30 Arthur Zamarin
2023-05-02 19:30 Arthur Zamarin
2023-05-02 19:02 Arthur Zamarin
2023-05-02 18:18 Arthur Zamarin
2023-05-02 18:16 Arthur Zamarin
2023-05-02 17:53 Arthur Zamarin
2023-05-02 17:44 Arthur Zamarin
2023-03-30 3:58 Matt Turner
2022-12-22 11:13 Arthur Zamarin
2022-12-22 11:13 Arthur Zamarin
2022-12-16 20:30 Arthur Zamarin
2022-12-16 20:30 Arthur Zamarin
2022-10-13 0:27 Matt Turner
2022-10-01 22:27 Matt Turner
2022-10-01 15:41 Matt Turner
2022-09-30 18:37 Arthur Zamarin
2022-09-28 16:29 Arthur Zamarin
2022-09-19 1:38 Sam James
2022-09-07 2:10 Matt Turner
2022-07-27 15:53 Matt Turner
2022-07-26 22:02 Matt Turner
2022-07-21 0:13 Sam James
2022-07-18 17:44 Sam James
2022-05-18 8:00 WANG Xuerui
2022-01-02 7:11 Sam James
2021-05-28 19:18 Sam James
2021-05-21 0:51 Yixun Lan
2021-04-13 15:03 Sam James
2021-01-25 3:22 Matt Turner
2020-11-06 6:57 Sam James
2020-08-31 2:52 Sam James
2020-08-30 18:28 Sam James
2020-04-17 19:50 Mart Raudsepp
2020-04-14 17:05 Mart Raudsepp
2020-02-11 10:52 Agostino Sarubbo
2020-02-09 15:56 Mart Raudsepp
2020-02-09 15:56 Mart Raudsepp
2020-01-28 7:41 Agostino Sarubbo
2020-01-27 14:28 Agostino Sarubbo
2020-01-27 12:44 Agostino Sarubbo
2020-01-27 8:10 Sergei Trofimovich
2020-01-11 12:10 Mart Raudsepp
2020-01-11 12:10 Mart Raudsepp
2019-12-25 20:28 Mart Raudsepp
2019-12-04 21:41 Matt Turner
2019-10-09 8:27 Agostino Sarubbo
2019-05-21 3:17 Aaron Bauman
2019-03-26 22:15 Mart Raudsepp
2019-02-17 16:01 Mikle Kolyada
2019-01-27 20:34 Dennis Lamm
2019-01-18 16:30 Mart Raudsepp
2018-12-28 3:46 Matt Turner
2018-10-29 1:01 Matt Turner
2018-10-27 18:43 Sergei Trofimovich
2018-10-26 20:19 Sergei Trofimovich
2018-09-22 19:54 Mart Raudsepp
2016-12-06 19:50 Markus Meier
2016-09-04 23:20 Gilles Dartiguelongue
2016-06-24 20:06 Pacho Ramos
2016-06-12 9:13 Pacho Ramos
2016-05-03 19:20 Markus Meier
2015-12-30 14:57 Jeroen Roovers
2015-11-14 15:27 Pacho Ramos
2015-11-14 15:27 Pacho Ramos
2015-10-03 8:11 Markus Meier
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=1667082747.b84e9801399f94be495b709d97e9bfecfb082bad.mattst88@gentoo \
--to=mattst88@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