From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-db/mydumper/
Date: Thu, 23 Mar 2017 20:53:01 +0000 (UTC) [thread overview]
Message-ID: <1490302288.e97dded5dd4bfc3f1db99f7da0ef31b822af9160.soap@gentoo> (raw)
commit: e97dded5dd4bfc3f1db99f7da0ef31b822af9160
Author: Harri Nieminen <moikkis <AT> gmail <DOT> com>
AuthorDate: Mon Mar 20 09:13:09 2017 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Thu Mar 23 20:51:28 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e97dded5
dev-db/mydumper: Fix toolong DESCRIPTION
Package-Manager: Portage-2.3.5, Repoman-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/4253
dev-db/mydumper/mydumper-0.6.2.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-db/mydumper/mydumper-0.6.2.ebuild b/dev-db/mydumper/mydumper-0.6.2.ebuild
index 943b153d4fe..b28500bd888 100644
--- a/dev-db/mydumper/mydumper-0.6.2.ebuild
+++ b/dev-db/mydumper/mydumper-0.6.2.ebuild
@@ -1,10 +1,10 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=5
inherit cmake-utils versionator
-DESCRIPTION="A high-performance multi-threaded backup (and restore) toolset for MySQL and Drizzle"
+DESCRIPTION="A high-performance multi-threaded backup toolset for MySQL and Drizzle"
HOMEPAGE="https://launchpad.net/mydumper"
SRC_URI="https://launchpad.net/mydumper/$(get_version_component_range 1-2)/${PV}/+download/${P}.tar.gz"
LICENSE="GPL-3"
next reply other threads:[~2017-03-23 20:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 20:53 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-01 10:30 [gentoo-commits] repo/gentoo:master commit in: dev-db/mydumper/ Jonas Stein
2017-10-08 12:29 Amy Liffey
2018-05-24 10:23 Amy Liffey
2018-10-02 9:33 Thomas Deutschmann
2019-01-07 17:00 Lars Wendler
2021-02-04 22:27 Thomas Deutschmann
2021-02-04 22:27 Thomas Deutschmann
2021-02-05 10:40 Sam James
2021-04-16 6:26 Joonas Niilola
2021-05-23 22:28 Agostino Sarubbo
2021-08-08 19:21 Ionen Wolkens
2021-08-08 19:21 Ionen Wolkens
2021-09-29 14:07 Sam James
2021-10-15 10:22 Joonas Niilola
2021-10-15 10:22 Joonas Niilola
2021-10-15 10:22 Joonas Niilola
2021-12-09 16:22 Agostino Sarubbo
2022-01-07 5:14 Sam James
2022-01-07 5:14 Sam James
2022-02-06 19:47 Ionen Wolkens
2022-04-29 12:20 Joonas Niilola
2022-05-13 20:04 Sam James
2022-08-04 6:37 Joonas Niilola
2022-08-04 6:37 Joonas Niilola
2022-10-25 17:55 Sam James
2022-11-10 16:15 Joonas Niilola
2023-02-15 5:53 Sam James
2023-04-17 11:56 Sam James
2023-04-26 4:03 Sam James
2023-06-23 20:16 Sam James
2023-07-14 6:50 Joonas Niilola
2023-07-14 6:50 Joonas Niilola
2023-08-19 4:26 Sam James
2023-09-01 17:15 Arthur Zamarin
2023-09-01 17:15 Arthur Zamarin
2023-10-21 8:43 Joonas Niilola
2023-11-02 10:25 Sam James
2024-03-07 16:33 Petr Vaněk
2024-03-07 16:33 Petr Vaněk
2024-03-07 16:33 Petr Vaněk
2024-03-11 14:24 Sam James
2024-10-18 7:06 Arthur Zamarin
2024-12-01 12:12 Sam James
2025-01-03 16:41 Joonas Niilola
2025-01-03 16:41 Joonas Niilola
2025-03-01 0:02 Jakov Smolić
2025-03-10 2:28 Sam James
2025-04-28 14:39 Sam James
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=1490302288.e97dded5dd4bfc3f1db99f7da0ef31b822af9160.soap@gentoo \
--to=soap@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