public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libpulse/
Date: Mon, 30 Oct 2023 05:15:22 +0000 (UTC)	[thread overview]
Message-ID: <1698642875.706b979f22ab83e8880e050f9fe1e84f30082f68.sam@gentoo> (raw)

commit:     706b979f22ab83e8880e050f9fe1e84f30082f68
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 30 05:14:35 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Oct 30 05:14:35 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=706b979f

media-libs/libpulse: add freedesktop-gitlab upstream metadata

Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-libs/libpulse/metadata.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/media-libs/libpulse/metadata.xml b/media-libs/libpulse/metadata.xml
index e1b0ba44ee04..fc9c7d5c17ad 100644
--- a/media-libs/libpulse/metadata.xml
+++ b/media-libs/libpulse/metadata.xml
@@ -22,4 +22,7 @@
     <flag name="asyncns">Use libasyncns for asynchronous name resolution.</flag>
     <flag name="doc">Build the doxygen-described API documentation.</flag>
   </use>
+  <upstream>
+    <remote-id type="freedesktop-gitlab">pulseaudio/pulseaudio</remote-id>
+  </upstream>
 </pkgmetadata>


             reply	other threads:[~2023-10-30  5:15 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  5:15 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-22  5:45 [gentoo-commits] repo/gentoo:master commit in: media-libs/libpulse/ Ionen Wolkens
2024-03-13  0:54 Sam James
2024-03-05 18:00 Arthur Zamarin
2024-03-05 18:00 Arthur Zamarin
2024-03-05 17:59 Arthur Zamarin
2024-03-04 11:24 Sam James
2024-03-02 22:07 Sam James
2024-03-02 18:18 Arthur Zamarin
2024-02-24 11:29 Sam James
2024-02-22 20:33 Arthur Zamarin
2024-02-07  4:55 Ionen Wolkens
2024-02-07  4:55 Ionen Wolkens
2024-02-07  4:55 Ionen Wolkens
2024-02-07  4:55 Ionen Wolkens
2024-02-02  2:29 Sam James
2024-01-17  2:46 Ionen Wolkens
2024-01-03 10:40 Sam James
2023-11-25  5:36 Sam James
2023-10-23  1:44 Sam James
2023-10-06 12:09 Sam James
2023-05-14 17:11 Sam James
2023-03-31 11:44 Arthur Zamarin
2023-03-31 11:44 Arthur Zamarin
2023-03-31 11:44 Arthur Zamarin
2023-03-31 11:44 Arthur Zamarin
2023-03-07 17:18 Sam James
2023-02-01 16:12 Arthur Zamarin
2023-01-27  6:21 Sam James
2022-10-28 19:53 Sam James
2022-09-26 16:11 Sam James
2022-07-31  3:29 Sam James
2022-07-31  3:29 Sam James
2022-07-31  3:29 Sam James
2022-07-31  3:29 Sam James
2022-07-29  8:02 Agostino Sarubbo
2022-07-29  3:18 Sam James
2022-07-29  1:53 Sam James
2022-07-04 21:40 Sam James
2022-06-23  4:29 Sam James
2022-06-12  8:32 Agostino Sarubbo
2022-06-12  8:30 Agostino Sarubbo
2022-06-11  7:40 Agostino Sarubbo
2022-06-11  7:40 Agostino Sarubbo
2022-06-11  7:39 Agostino Sarubbo
2022-06-11  7:37 Agostino Sarubbo
2022-06-10  8:10 Sam James
2022-06-10  6:56 Sam James
2022-05-29  6:45 Sam James
2022-05-28 19:19 Sam James
2022-04-28 16:00 Sam James
2022-02-27  1:04 Sam James
2022-02-22 20:54 Sam James
2021-12-28 22:26 Sam James
2021-09-24 20:33 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=1698642875.706b979f22ab83e8880e050f9fe1e84f30082f68.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