public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdazzle/
Date: Sat, 29 Oct 2022 23:21:09 +0000 (UTC)	[thread overview]
Message-ID: <1667085610.73d884f68a9d754b030a0a6ddff5839d5b3902b0.mattst88@gentoo> (raw)

commit:     73d884f68a9d754b030a0a6ddff5839d5b3902b0
Author:     Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 29 21:19:46 2022 +0000
Commit:     Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sat Oct 29 23:20:10 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=73d884f6

dev-libs/libdazzle: Set remote-id

Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>

 dev-libs/libdazzle/metadata.xml | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/dev-libs/libdazzle/metadata.xml b/dev-libs/libdazzle/metadata.xml
index 01065172e304..6ca5bc16c6d2 100644
--- a/dev-libs/libdazzle/metadata.xml
+++ b/dev-libs/libdazzle/metadata.xml
@@ -1,12 +1,17 @@
 <?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>
-	<longdescription>libdazzle is a collection of fancy features for GLib and Gtk+ that aren't quite
-		ready or generic enough for use inside those libraries. This is often a proving
-		ground for new widget prototypes. Applications such as Builder tend to drive
-		development of this project.</longdescription>
+  <maintainer type="project">
+    <email>gnome@gentoo.org</email>
+    <name>Gentoo GNOME Desktop</name>
+  </maintainer>
+  <longdescription>
+    libdazzle is a collection of fancy features for GLib and Gtk+ that aren't
+    quite ready or generic enough for use inside those libraries. This is
+    often a proving ground for new widget prototypes. Applications such as
+    Builder tend to drive development of this project.
+  </longdescription>
+  <upstream>
+    <remote-id type="gnome-gitlab">GNOME/libdazzle</remote-id>
+  </upstream>
 </pkgmetadata>


             reply	other threads:[~2022-10-29 23:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 23:21 Matt Turner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-24 10:46 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdazzle/ WANG Xuerui
2022-03-22  2:46 Matt Turner
2021-12-18 23:39 Matt Turner
2021-09-28 14:53 Yixun Lan
2021-04-12 21:59 Matt Turner
2021-04-12 21:59 Matt Turner
2020-12-08 11:46 Mart Raudsepp
2020-07-17 10:20 Mart Raudsepp
2020-03-01 16:18 Mart Raudsepp
2019-12-23 21:26 Mart Raudsepp
2019-10-27 12:16 Mart Raudsepp
2019-08-05  0:34 Aaron Bauman
2019-07-28 20:22 Mart Raudsepp
2019-07-27  6:49 Mart Raudsepp
2019-01-14 19:52 Mart Raudsepp
2019-01-14 14:39 Mikle Kolyada
2019-01-09  1:39 Thomas Deutschmann
2018-12-19 22:31 Sergei Trofimovich
2018-12-19 22:31 Sergei Trofimovich
2018-12-02 13:34 Mikle Kolyada
2018-10-09 21:14 Sergei Trofimovich
2018-09-12 14:39 Thomas Deutschmann
2018-08-29 21:57 Mart Raudsepp

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=1667085610.73d884f68a9d754b030a0a6ddff5839d5b3902b0.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