From: "Esteve Varela Colominas" <esteve.varela@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-libs/libglibutil/
Date: Thu, 21 Mar 2024 22:11:01 +0000 (UTC) [thread overview]
Message-ID: <1711059043.0ce36c5cc687e9d162523df0596e6ecb690b5fe2.esteve.varela@gentoo> (raw)
commit: 0ce36c5cc687e9d162523df0596e6ecb690b5fe2
Author: Esteve Varela Colominas <esteve.varela <AT> gmail <DOT> com>
AuthorDate: Thu Mar 21 19:00:27 2024 +0000
Commit: Esteve Varela Colominas <esteve.varela <AT> gmail <DOT> com>
CommitDate: Thu Mar 21 22:10:43 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=0ce36c5c
dev-libs/libglibutil: Remove <longdescription> in metadata
It's not required, and it's better to signal that it's missing rather
than having one that matches DESCRIPTION.
Signed-off-by: Esteve Varela Colominas <esteve.varela <AT> gmail.com>
dev-libs/libglibutil/metadata.xml | 3 ---
1 file changed, 3 deletions(-)
diff --git a/dev-libs/libglibutil/metadata.xml b/dev-libs/libglibutil/metadata.xml
index 6cbc93b73a..8aef270ae1 100644
--- a/dev-libs/libglibutil/metadata.xml
+++ b/dev-libs/libglibutil/metadata.xml
@@ -6,9 +6,6 @@
<name>Denis Reva</name>
<description>rarogcmex</description>
</maintainer>
- <longdescription lang="en">
- Library of glib utilities from sailfish os.
- </longdescription>
<upstream>
<remote-id type="github">sailfishos/libglibutil</remote-id>
</upstream>
next reply other threads:[~2024-03-21 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 22:11 Esteve Varela Colominas [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 15:48 [gentoo-commits] repo/proj/guru:dev commit in: dev-libs/libglibutil/ Denis Reva
2024-08-08 8:58 Denis Reva
2024-08-08 8:58 Denis Reva
2024-03-21 22:11 Esteve Varela Colominas
2024-02-19 13:21 Denis Reva
2022-12-21 14:10 Denis Reva
2022-12-18 13:40 Denis Reva
2022-12-18 13:38 Denis Reva
2022-12-18 13:34 Denis Reva
2022-12-18 9:37 Denis Reva
2022-05-12 6:13 Pascal Jäger
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=1711059043.0ce36c5cc687e9d162523df0596e6ecb690b5fe2.esteve.varela@gentoo \
--to=esteve.varela@gmail.com \
--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