public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-apps/dolphin/
Date: Mon, 12 Aug 2024 19:12:27 +0000 (UTC)	[thread overview]
Message-ID: <1723489722.54293a36e0594f61f9fc1c85a67cb4d9c0e7af27.asturm@gentoo> (raw)

commit:     54293a36e0594f61f9fc1c85a67cb4d9c0e7af27
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 12 19:08:42 2024 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Mon Aug 12 19:08:42 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=54293a36

kde-apps/dolphin: add kde-invent upstream metadata

Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>

 kde-apps/dolphin/metadata.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/kde-apps/dolphin/metadata.xml b/kde-apps/dolphin/metadata.xml
index e2e43d1a3d95..252250e2ffa6 100644
--- a/kde-apps/dolphin/metadata.xml
+++ b/kde-apps/dolphin/metadata.xml
@@ -6,7 +6,8 @@
 		<name>Gentoo KDE Project</name>
 	</maintainer>
 	<upstream>
-		<bugs-to>https://bugs.kde.org/</bugs-to>
+		<bugs-to>https://bugs.kde.org/enter_bug.cgi?product=dolphin</bugs-to>
+		<remote-id type="kde-invent">system/dolphin</remote-id>
 	</upstream>
 	<use>
 		<flag name="activities">Track which folders are frequently accessed on a Plasma desktop</flag>


             reply	other threads:[~2024-08-12 19:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 19:12 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-10 11:31 [gentoo-commits] repo/gentoo:master commit in: kde-apps/dolphin/ WANG Xuerui
2024-12-20 17:29 Andreas Sturmlechner
2024-12-20 17:29 Andreas Sturmlechner
2024-11-20 17:42 Andreas Sturmlechner
2024-10-07  5:41 Arthur Zamarin
2024-08-29 19:03 Andreas Sturmlechner
2024-08-29 15:48 Arthur Zamarin
2024-08-16 19:57 Arthur Zamarin
2024-08-16 19:37 Arthur Zamarin
2024-08-15 17:48 Andreas Sturmlechner
2024-08-15 17:48 Andreas Sturmlechner
2024-01-03 21:55 Andreas Sturmlechner
2023-12-21 14:52 Andreas Sturmlechner
2023-12-17 23:02 Andreas Sturmlechner
2022-12-14 20:01 Andreas Sturmlechner
2022-11-01  5:34 WANG Xuerui
2022-03-03 14:54 Andreas Sturmlechner
2022-02-06 21:17 Andreas Sturmlechner
2022-02-06 21:17 Andreas Sturmlechner
2021-04-04 13:23 Andreas Sturmlechner
2021-01-23  0:25 Andreas Sturmlechner
2020-12-23 21:32 Andreas Sturmlechner
2020-05-20 15:33 Andreas Sturmlechner
2020-05-20 13:32 Mikle Kolyada
2020-05-20  9:50 Mikle Kolyada
2020-05-19 19:32 Mikle Kolyada
2020-02-15 13:43 Andreas Sturmlechner
2019-07-29 15:53 Aaron Bauman
2019-04-03 12:02 Andreas Sturmlechner
2018-12-01 17:00 Mikle Kolyada
2018-07-21 16:51 Andreas Sturmlechner
2018-05-24 13:27 Andreas Sturmlechner
2017-11-30  2:07 Thomas Deutschmann
2016-08-04 21:10 Maciej Mrozowski
2016-06-29 15:32 Michael Palimaka
2016-06-28 21:14 Michael Palimaka
2016-04-07 12:03 Michael Palimaka
2016-03-06 10:26 Mikle Kolyada
2016-03-05 12:06 Mikle Kolyada
2016-01-04 18:12 Michael Palimaka
2015-09-30 14:17 Michael Palimaka

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=1723489722.54293a36e0594f61f9fc1c85a67cb4d9c0e7af27.asturm@gentoo \
    --to=asturm@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