From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-video/kaffeine/
Date: Thu, 25 Jan 2018 14:41:46 +0000 (UTC) [thread overview]
Message-ID: <1516891296.4b49c8f2b5b938ab2c1bd3fe8c55ed3ae09be529.kensington@gentoo> (raw)
commit: 4b49c8f2b5b938ab2c1bd3fe8c55ed3ae09be529
Author: Michael Palimaka <kensington <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 25 14:31:12 2018 +0000
Commit: Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Thu Jan 25 14:41:36 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4b49c8f2
media-video/kaffeine: remove obsolete upstream metadata
Package-Manager: Portage-2.3.19, Repoman-2.3.6
media-video/kaffeine/metadata.xml | 3 ---
1 file changed, 3 deletions(-)
diff --git a/media-video/kaffeine/metadata.xml b/media-video/kaffeine/metadata.xml
index 81fb67df1eb..00c71c8a23d 100644
--- a/media-video/kaffeine/metadata.xml
+++ b/media-video/kaffeine/metadata.xml
@@ -9,7 +9,4 @@
<email>kde@gentoo.org</email>
<name>Gentoo KDE Project</name>
</maintainer>
- <upstream>
- <remote-id type="sourceforge">kaffeine</remote-id>
- </upstream>
</pkgmetadata>
next reply other threads:[~2018-01-25 14:41 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 14:41 Michael Palimaka [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 23:14 [gentoo-commits] repo/gentoo:master commit in: media-video/kaffeine/ Andreas Sturmlechner
2024-11-22 23:14 Andreas Sturmlechner
2024-09-17 16:00 Sam James
2024-09-07 14:27 Sam James
2022-10-04 7:31 Agostino Sarubbo
2022-09-30 20:39 Sam James
2021-06-05 10:55 Mikle Kolyada
2021-06-05 10:53 Mikle Kolyada
2019-12-25 16:02 Andreas Sturmlechner
2019-06-20 10:37 Andreas Sturmlechner
2019-06-20 9:24 Mikle Kolyada
2019-06-18 18:24 Thomas Deutschmann
2019-05-15 10:38 Andreas Sturmlechner
2019-02-22 11:25 Mikle Kolyada
2019-02-15 18:29 Thomas Deutschmann
2019-02-07 15:15 Andreas Sturmlechner
2019-01-16 8:17 Andreas Sturmlechner
2018-07-09 16:23 Johannes Huber
2018-07-09 14:53 Mikle Kolyada
2018-07-04 3:17 Thomas Deutschmann
2018-05-05 14:43 Johannes Huber
2018-01-25 14:41 Michael Palimaka
2018-01-25 14:41 Michael Palimaka
2017-12-05 23:35 Andreas Sturmlechner
2017-12-02 18:33 Andreas Sturmlechner
2017-11-07 17:57 Thomas Deutschmann
2017-11-06 18:19 Andreas Sturmlechner
2017-11-06 18:19 Andreas Sturmlechner
2017-11-06 11:41 Manuel Rüger
2017-09-15 18:14 Johannes Huber
2017-09-15 11:55 Michael Palimaka
2017-08-20 2:25 Michael Palimaka
2017-07-19 16:33 Andreas Sturmlechner
2017-04-27 12:17 Michael Palimaka
2017-03-11 19:40 Johannes Huber
2017-03-10 22:58 Michael Palimaka
2017-02-22 20:46 Johannes Huber
2016-11-19 18:54 Johannes Huber
2016-11-19 18:44 Michael Palimaka
2016-10-09 16:17 Michael Palimaka
2016-08-05 16:59 Michael Palimaka
2016-08-05 16:59 Michael Palimaka
2016-07-07 17:52 Michael Palimaka
2016-07-01 16:36 Johannes Huber
2016-06-23 16:03 Michael Palimaka
2016-06-23 16:03 Michael Palimaka
2016-06-12 7:52 Johannes Huber
2016-06-08 11:11 Johannes Huber
2016-06-03 14:42 Johannes Huber
2016-06-03 14:37 Johannes Huber
2016-04-11 18:14 Johannes Huber
2015-09-07 9:11 Lars Wendler
2015-09-07 8:56 Lars Wendler
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=1516891296.4b49c8f2b5b938ab2c1bd3fe8c55ed3ae09be529.kensington@gentoo \
--to=kensington@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