public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthew Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/keystoneauth/
Date: Wed, 25 Mar 2020 16:17:21 +0000 (UTC)	[thread overview]
Message-ID: <1585153036.095f26a92990bdc789ed268678f492d0f76c6640.prometheanfire@gentoo> (raw)

commit:     095f26a92990bdc789ed268678f492d0f76c6640
Author:     Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 25 16:14:33 2020 +0000
Commit:     Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Wed Mar 25 16:17:16 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=095f26a9

dev-python/keystoneauth: fix metadata

Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Matthew Thode <prometheanfire <AT> gentoo.org>

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

diff --git a/dev-python/keystoneauth/metadata.xml b/dev-python/keystoneauth/metadata.xml
index 89e7da46475..649f2c12e07 100644
--- a/dev-python/keystoneauth/metadata.xml
+++ b/dev-python/keystoneauth/metadata.xml
@@ -5,9 +5,6 @@
 		<email>prometheanfire@gentoo.org</email>
 		<name>Matthew Thode</name>
 	</maintainer>
-	<longdescription lang="en">
-		This package contains tools for authenticating to an OpenStack-based cloud.
-	</longdescription>
 	<upstream>
 		<remote-id type="github">openstack/keystoneauth</remote-id>
 		<remote-id type="pypi">keystoneauth1</remote-id>


             reply	other threads:[~2020-03-25 16:17 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 16:17 Matthew Thode [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-14 16:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/keystoneauth/ Michał Górny
2023-01-04 14:15 Michał Górny
2022-12-25 17:45 Michał Górny
2022-12-25 16:42 Sam James
2022-11-25  5:14 Michał Górny
2022-11-12 11:59 Arthur Zamarin
2022-08-17 19:31 Arthur Zamarin
2022-08-17 18:52 Arthur Zamarin
2022-07-15 18:30 Arthur Zamarin
2022-06-28 19:42 Michał Górny
2022-06-28 19:30 Arthur Zamarin
2022-05-28 21:12 Jakov Smolić
2022-05-21  6:47 Michał Górny
2022-04-01 18:45 Michał Górny
2022-04-01 17:33 Arthur Zamarin
2022-04-01 17:33 Arthur Zamarin
2022-04-01 17:32 Arthur Zamarin
2022-03-09 18:26 Arthur Zamarin
2022-02-24 18:08 Michał Górny
2021-12-17  9:15 Michał Górny
2021-10-24  5:13 Arthur Zamarin
2021-10-24  1:15 Sam James
2021-09-17 22:22 Michał Górny
2021-07-07  6:33 Michał Górny
2021-07-07  2:17 Sam James
2021-06-26  2:55 Sam James
2021-06-24 23:57 Sam James
2021-06-23 10:13 Michał Górny
2021-06-23 10:09 Michał Górny
2021-06-23 10:09 Michał Górny
2020-11-16  0:02 Michał Górny
2020-11-15 23:50 Sam James
2020-11-14 21:52 Michał Górny
2020-10-10 23:09 Matthew Thode
2020-10-10 20:34 Matthew Thode
2020-07-18 22:30 Matthew Thode
2020-07-17  1:52 Sam James
2020-07-01 16:27 Matthew Thode
2020-06-20 19:23 Matthew Thode
2020-05-30 17:52 Matthew Thode
2020-05-16 21:21 Matthew Thode
2020-03-25 16:17 Matthew Thode
2020-02-25 17:52 Matthew Thode
2020-02-25 16:48 Matthew Thode
2019-11-19 18:36 Matthew Thode
2019-10-21  0:19 Matthew Thode
2019-05-11 18:17 Matthew Thode
2019-04-09  7:06 Matthew Thode
2018-08-30 21:34 Matt Thode
2018-02-16  6:08 Matt Thode
2018-02-16  6:08 Matt Thode
2017-08-28  0:47 Matt Thode
2017-08-28  0:47 Matt Thode
2017-06-04  7:30 Justin Lecher
2017-03-13  1:30 Zac Medico
2017-02-27  2:16 Matt Thode
2017-02-24 17:39 Matt Thode
2017-02-24 17:39 Matt Thode
2017-01-31 15:45 Matt Thode
2016-11-17 18:40 Matt Thode
2016-10-19  4:09 Matt Thode
2016-05-24 23:16 Matt Thode
2016-03-29 18:31 Matt Thode
2016-03-29 18:31 Matt Thode
2016-03-28  2:40 Matt Thode
2016-03-25  5:02 Matt Thode

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=1585153036.095f26a92990bdc789ed268678f492d0f76c6640.prometheanfire@gentoo \
    --to=prometheanfire@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