public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-ironicclient/
Date: Sun, 12 Jul 2020 16:57:45 +0000 (UTC)	[thread overview]
Message-ID: <1594572992.ba78e9bd3de542c19e56afa6cbd80d6db7f808d4.mgorny@gentoo> (raw)

commit:     ba78e9bd3de542c19e56afa6cbd80d6db7f808d4
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 12 16:49:31 2020 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Jul 12 16:56:32 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba78e9bd

dev-python/python-ironicclient: Remove useless longdesc

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/python-ironicclient/metadata.xml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/dev-python/python-ironicclient/metadata.xml b/dev-python/python-ironicclient/metadata.xml
index cc25c556f9b..5c21eab672f 100644
--- a/dev-python/python-ironicclient/metadata.xml
+++ b/dev-python/python-ironicclient/metadata.xml
@@ -5,9 +5,6 @@
 		<email>prometheanfire@gentoo.org</email>
 		<name>Matthew Thode</name>
 	</maintainer>
-	<longdescription lang="en">
-		API bindings and client for the OpenStack bare metal provisioning service.
-	</longdescription>
 	<upstream>
 		<remote-id type="pypi">python-ironicclient</remote-id>
 	</upstream>


             reply	other threads:[~2020-07-12 16:57 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 16:57 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-30  1:56 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-ironicclient/ Michał Górny
2024-07-04  5:13 Michał Górny
2024-05-25  6:36 Arthur Zamarin
2024-05-22  8:03 Michał Górny
2024-05-09  4:08 Michał Górny
2024-03-16 12:08 Michał Górny
2024-03-16 11:48 Arthur Zamarin
2024-03-01  4:47 Michał Górny
2023-12-05 15:30 Michał Górny
2023-10-06 15:52 Michał Górny
2023-10-06 15:14 Sam James
2023-09-02  3:22 Michał Górny
2023-08-11 19:12 Michał Górny
2023-08-11 19:09 Arthur Zamarin
2023-07-07  3:15 Michał Górny
2023-06-11 16:18 Michał Górny
2023-06-11 15:04 Sam James
2023-05-11 17:58 Michał Górny
2023-03-25  9:22 Michał Górny
2023-03-25  6:07 Sam James
2023-03-06 15:10 Michał Górny
2023-02-17 18:51 Michał Górny
2022-10-03  6:56 Michał Górny
2022-10-03  0:44 Sam James
2022-08-31 19:08 Arthur Zamarin
2022-08-18 10:17 Michał Górny
2022-08-18  7:01 Agostino Sarubbo
2022-07-15 18:30 Arthur Zamarin
2022-07-15 18:30 Arthur Zamarin
2022-07-15 18:30 Arthur Zamarin
2022-06-05  5:46 Michał Górny
2022-04-01 18:49 Michał Górny
2022-04-01 18:34 Arthur Zamarin
2022-04-01 18:34 Arthur Zamarin
2022-02-25 23:41 Michał Górny
2022-02-13  9:42 Michał Górny
2022-02-13  8:41 Jakov Smolić
2022-02-13  8:41 Jakov Smolić
2022-01-07 16:49 Arthur Zamarin
2021-11-19  6:18 Arthur Zamarin
2021-11-05 19:28 Michał Górny
2021-11-05 18:35 Sam James
2021-11-05 17:34 Sam James
2021-10-18 20:40 Michał Górny
2021-10-04 22:58 Sam James
2021-09-30 17:59 Arthur Zamarin
2021-05-31 20:42 Michał Górny
2020-12-02 23:31 Thomas Deutschmann
2020-12-02 22:58 Sam James
2020-10-17  3:06 Matthew Thode
2020-10-15 22:13 Matthew Thode
2020-05-30 17:52 Matthew Thode
2020-05-13  0:00 Matthew Thode
2020-02-11 19:06 Matthew Thode
2019-06-04 15:11 Matthew Thode
2019-05-15 20:16 Matthew Thode
2019-05-08  4:22 Matthew Thode
2018-09-01  5:30 Matt Thode
2018-08-01 17:03 Matt Thode
2018-06-24 19:21 Pacho Ramos
2017-09-29 23:32 Matt Thode
2017-09-13 17:39 Matt Thode
2017-03-22 16:03 Matt Thode
2016-12-17  2:42 Matt Thode
2016-11-22  5:08 Matt Thode
2015-11-16 16:26 Agostino Sarubbo
2015-11-16 16:15 Agostino Sarubbo
2015-11-14  0:09 Matt Thode
2015-10-15  9:08 Matt Thode
2015-08-21  6:42 Agostino Sarubbo
2015-08-21  6:41 Agostino Sarubbo

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=1594572992.ba78e9bd3de542c19e56afa6cbd80d6db7f808d4.mgorny@gentoo \
    --to=mgorny@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