public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/grpcio/
Date: Sat, 22 Feb 2020 01:30:13 +0000 (UTC)	[thread overview]
Message-ID: <1582334993.404fa22bcec6e27ee234616cc73bff3948604439.gyakovlev@gentoo> (raw)

commit:     404fa22bcec6e27ee234616cc73bff3948604439
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 21 21:36:42 2020 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Sat Feb 22 01:29:53 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=404fa22b

dev-python/grpcio: QA: RedundantLongDescription

Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

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

diff --git a/dev-python/grpcio/metadata.xml b/dev-python/grpcio/metadata.xml
index 011f4a88ece..8ab14201ea3 100644
--- a/dev-python/grpcio/metadata.xml
+++ b/dev-python/grpcio/metadata.xml
@@ -5,9 +5,6 @@
 		<email>gyakovlev@gentoo.org</email>
 		<name>Georgy Yakovlev</name>
 	</maintainer>
-	<longdescription lang="en">
-		High-performance RPC framework (python libraries)
-	</longdescription>
 	<upstream>
 		<remote-id type="github">grpc/grpc</remote-id>
 		<remote-id type="pypi">grpcio</remote-id>


             reply	other threads:[~2020-02-22  1:30 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-22  1:30 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-10  9:39 [gentoo-commits] repo/gentoo:master commit in: dev-python/grpcio/ Sam James
2024-11-09 13:24 Arthur Zamarin
2024-10-29  6:51 Michał Górny
2024-10-26 17:48 Michał Górny
2024-10-23 15:02 Michał Górny
2024-03-21  5:58 Sam James
2024-01-14  3:16 Sam James
2023-11-29 11:45 Arthur Zamarin
2023-11-29 10:15 Michał Górny
2023-11-29 10:03 Michał Górny
2023-11-24 15:12 Arthur Zamarin
2023-11-06 14:41 Sam James
2023-07-28  9:32 Sam James
2023-03-16  3:50 Michał Górny
2023-01-05  9:01 Sam James
2023-01-05  8:53 Sam James
2022-11-28 22:21 Georgy Yakovlev
2022-11-28 21:45 Georgy Yakovlev
2022-02-04 10:27 Michał Górny
2022-02-04  9:12 Jakov Smolić
2022-02-04  7:28 Agostino Sarubbo
2021-12-20  5:04 Georgy Yakovlev
2021-12-18 15:39 Michał Górny
2021-12-18 15:09 Arthur Zamarin
2021-11-14  1:59 Georgy Yakovlev
2021-11-13 21:24 Michał Górny
2021-11-13 20:40 Jakov Smolić
2021-11-13  9:47 Jakov Smolić
2021-10-06 12:15 Arthur Zamarin
2021-07-25  1:04 Sam James
2021-07-24 15:12 Sam James
2021-06-29  5:53 Yixun Lan
2021-06-21 23:31 Georgy Yakovlev
2021-06-21 23:31 Georgy Yakovlev
2021-06-15  2:57 Georgy Yakovlev
2021-06-05 20:43 Sam James
2021-06-05 20:35 Sam James
2021-05-30  1:43 Georgy Yakovlev
2021-04-29 23:35 Georgy Yakovlev
2021-04-29  8:29 Georgy Yakovlev
2020-12-17 17:09 Michał Górny
2020-12-10 22:04 Thomas Deutschmann
2020-10-09 21:42 Georgy Yakovlev
2020-09-20 20:21 Agostino Sarubbo
2020-08-31 20:54 Thomas Deutschmann
2020-08-09 23:09 Zac Medico
2020-06-06 18:01 Michał Górny
2020-04-20  7:28 Georgy Yakovlev
2020-02-05 20:12 Georgy Yakovlev
2020-02-05 14:05 Michał Górny
2020-01-17 10:22 Georgy Yakovlev
2019-12-22  3:28 Georgy Yakovlev
2019-11-16  0:31 Georgy Yakovlev
2019-10-26  0:11 Georgy Yakovlev
2019-08-17  3:00 Georgy Yakovlev
2019-08-17  3:00 Georgy Yakovlev
2019-08-17  3:00 Georgy Yakovlev
2019-08-17  3:00 Georgy Yakovlev
2019-07-14  1:10 Georgy Yakovlev
2019-05-28  4:53 Georgy Yakovlev
2019-05-08  3:01 Georgy Yakovlev
2019-05-07 23:56 Georgy Yakovlev
2019-04-30  4:42 Georgy Yakovlev
2019-02-27  4:20 Georgy Yakovlev
2019-01-16  0:52 Georgy Yakovlev
2019-01-16  0:52 Georgy Yakovlev
2018-12-15  6:00 Georgy Yakovlev
2018-12-10  4:50 Georgy Yakovlev
2018-11-15  3:21 Georgy Yakovlev
2018-10-25  6:40 Georgy Yakovlev

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=1582334993.404fa22bcec6e27ee234616cc73bff3948604439.gyakovlev@gentoo \
    --to=gyakovlev@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