From: "Stefan Strogin" <steils@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-video/openshot/
Date: Tue, 25 Feb 2020 05:44:25 +0000 (UTC) [thread overview]
Message-ID: <1582609436.940a8ed8e2700eec7da513b0748fb94f8db2ecad.steils@gentoo> (raw)
commit: 940a8ed8e2700eec7da513b0748fb94f8db2ecad
Author: Stefan Strogin <steils <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 25 05:41:59 2020 +0000
Commit: Stefan Strogin <steils <AT> gentoo <DOT> org>
CommitDate: Tue Feb 25 05:43:56 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=940a8ed8
media-video/openshot: remove redundant longdescription
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Stefan Strogin <steils <AT> gentoo.org>
media-video/openshot/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/media-video/openshot/metadata.xml b/media-video/openshot/metadata.xml
index 6e1e6c99fcf..483a95e5634 100644
--- a/media-video/openshot/metadata.xml
+++ b/media-video/openshot/metadata.xml
@@ -9,7 +9,6 @@
<email>media-video@gentoo.org</email>
<name>Gentoo Video project</name>
</maintainer>
- <longdescription>Free, open-source, non-linear video editor to create and edit videos and movies</longdescription>
<upstream>
<remote-id type="github">OpenShot/openshot-qt</remote-id>
<bugs-to>https://github.com/OpenShot/openshot-qt/issues</bugs-to>
next reply other threads:[~2020-02-25 5:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 5:44 Stefan Strogin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-07 20:55 [gentoo-commits] repo/gentoo:master commit in: media-video/openshot/ Sam James
2023-07-06 0:06 Sam James
2023-05-03 7:22 Sam James
2023-05-01 13:19 Sam James
2023-02-07 10:37 Andreas Sturmlechner
2022-06-10 6:48 Agostino Sarubbo
2022-06-09 7:39 Agostino Sarubbo
2022-06-07 5:17 Sam James
2022-02-04 18:40 Michał Górny
2021-11-21 16:17 Stefan Strogin
2021-10-27 15:33 Rick Farina
2021-09-04 21:01 Andreas Sturmlechner
2021-09-04 19:20 Stefan Strogin
2021-06-01 17:07 Andrew Ammerlaan
2021-05-30 19:04 Andreas Sturmlechner
2021-05-26 3:57 Stefan Strogin
2021-05-25 11:15 Sam James
2021-03-15 13:35 Andreas Sturmlechner
2021-02-21 10:16 Andreas Sturmlechner
2021-01-21 7:40 Agostino Sarubbo
2021-01-10 15:53 Andreas Sturmlechner
2021-01-10 15:53 Andreas Sturmlechner
2021-01-01 22:14 Andreas Sturmlechner
2021-01-01 22:14 Andreas Sturmlechner
2021-01-01 22:14 Andreas Sturmlechner
2020-12-03 15:42 Andreas Sturmlechner
2020-12-03 15:42 Andreas Sturmlechner
2020-05-16 2:44 Stefan Strogin
2020-02-10 19:59 Stefan Strogin
2019-12-15 14:46 Agostino Sarubbo
2019-12-15 12:44 Agostino Sarubbo
2019-08-14 2:33 Stefan Strogin
2019-06-13 15:31 Stefan Strogin
2019-06-13 15:31 Stefan Strogin
2018-05-01 7:36 Michał Górny
2018-02-06 15:10 Thomas Deutschmann
2017-12-06 19:52 Pacho Ramos
2017-10-03 22:14 Patrice Clement
2017-07-26 8:12 Michał Górny
2017-07-26 8:12 Michał Górny
2017-01-29 16:45 Michael Palimaka
2017-01-29 16:45 Michael Palimaka
2016-09-14 7:38 David Seifert
2016-07-04 0:05 Göktürk Yüksek
2016-07-04 0:05 Göktürk Yüksek
2016-04-25 13:17 Patrice Clement
2016-04-21 9:52 Ian Delaney
2016-04-18 8:13 Patrice Clement
2016-03-18 5:33 Ian Delaney
2016-03-16 10:03 Patrice Clement
2016-03-16 8:58 Ian Delaney
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=1582609436.940a8ed8e2700eec7da513b0748fb94f8db2ecad.steils@gentoo \
--to=steils@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