From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/mdds/
Date: Sun, 14 May 2023 17:11:16 +0000 (UTC) [thread overview]
Message-ID: <1684084254.c2eecc4942eee2304e4341411aaf1e63719dd9dd.sam@gentoo> (raw)
commit: c2eecc4942eee2304e4341411aaf1e63719dd9dd
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun May 14 17:10:29 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 14 17:10:54 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2eecc49
dev-util/mdds: add gitlab upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/mdds/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-util/mdds/metadata.xml b/dev-util/mdds/metadata.xml
index 7710a5aad70e..32078be15b6e 100644
--- a/dev-util/mdds/metadata.xml
+++ b/dev-util/mdds/metadata.xml
@@ -7,5 +7,6 @@
</maintainer>
<upstream>
<remote-id type="google-code">multidimalgorithm</remote-id>
+ <remote-id type="gitlab">mdds/mdds</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2023-05-14 17:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 17:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-20 20:49 [gentoo-commits] repo/gentoo:master commit in: dev-util/mdds/ Andreas Sturmlechner
2024-02-20 5:56 Sam James
2024-02-17 9:55 Arthur Zamarin
2024-02-12 10:31 Sam James
2024-01-27 0:48 Andreas Sturmlechner
2024-01-27 0:48 Andreas Sturmlechner
2023-08-30 23:52 Sam James
2023-02-25 10:27 Andreas Sturmlechner
2022-08-12 12:26 WANG Xuerui
2022-08-12 12:26 WANG Xuerui
2022-06-14 7:21 Agostino Sarubbo
2022-05-18 11:13 Andreas Sturmlechner
2022-05-15 10:55 Andreas Sturmlechner
2022-05-14 21:30 David Seifert
2022-04-27 21:57 Sam James
2022-04-10 10:46 Sam James
2022-03-12 15:53 Andreas Sturmlechner
2022-02-08 23:53 Andreas K. Hüttel
2021-12-29 13:46 Yixun Lan
2021-11-14 5:25 Sam James
2020-11-23 9:47 Sam James
2020-11-23 4:52 Sam James
2020-11-23 3:58 Sam James
2020-05-31 15:40 Mikle Kolyada
2020-05-28 17:09 Andreas Sturmlechner
2020-05-20 13:35 Mikle Kolyada
2020-05-19 19:36 Mikle Kolyada
2020-04-10 13:48 Andreas Sturmlechner
2020-03-16 21:29 Andreas Sturmlechner
2019-07-31 21:11 Aaron Bauman
2019-06-18 18:24 Thomas Deutschmann
2019-06-09 20:16 Mikle Kolyada
2019-03-12 7:10 Andreas Sturmlechner
2018-11-15 23:12 Andreas Sturmlechner
2018-09-16 22:34 Andreas Sturmlechner
2018-09-16 22:34 Andreas Sturmlechner
2018-09-12 20:56 Andreas Sturmlechner
2017-12-29 23:06 Andreas Sturmlechner
2017-12-29 18:03 Mikle Kolyada
2017-12-28 19:35 Andreas Sturmlechner
2017-12-26 0:59 Thomas Deutschmann
2017-11-19 23:49 Andreas Sturmlechner
2017-11-14 14:13 Manuel Rüger
2017-11-11 21:17 Andreas Sturmlechner
2017-11-11 21:17 Andreas Sturmlechner
2017-11-10 19:20 Andreas Sturmlechner
2017-11-10 19:20 Andreas Sturmlechner
2017-11-08 8:55 Andreas Sturmlechner
2016-12-17 15:57 Andreas Hüttel
2016-12-03 23:00 Andreas Hüttel
2016-11-29 18:41 Agostino Sarubbo
2016-11-29 18:40 Agostino Sarubbo
2016-09-17 21:32 Andreas Hüttel
2016-09-17 21:32 Andreas Hüttel
2016-06-03 12:50 Lars Wendler
2016-06-03 12:50 Lars Wendler
2016-06-03 12:50 Lars Wendler
2016-02-22 17:07 Andreas Hüttel
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=1684084254.c2eecc4942eee2304e4341411aaf1e63719dd9dd.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