From: "Brian Evans" <grknight@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Crypt_Blowfish/
Date: Mon, 10 Jul 2017 03:16:52 +0000 (UTC) [thread overview]
Message-ID: <1499655958.9d99d0c41b88c6c51730ad78c31e19790f2412ba.grknight@gentoo> (raw)
commit: 9d99d0c41b88c6c51730ad78c31e19790f2412ba
Author: Brian Evans <grknight <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 10 03:05:58 2017 +0000
Commit: Brian Evans <grknight <AT> gentoo <DOT> org>
CommitDate: Mon Jul 10 03:05:58 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d99d0c4
dev-php/PEAR-Crypt_Blowfish: Fix description
Package-Manager: Portage-2.3.6, Repoman-2.3.2
dev-php/PEAR-Crypt_Blowfish/PEAR-Crypt_Blowfish-1.1.0_rc2-r1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-php/PEAR-Crypt_Blowfish/PEAR-Crypt_Blowfish-1.1.0_rc2-r1.ebuild b/dev-php/PEAR-Crypt_Blowfish/PEAR-Crypt_Blowfish-1.1.0_rc2-r1.ebuild
index ac421f599f3..609493f2f4c 100644
--- a/dev-php/PEAR-Crypt_Blowfish/PEAR-Crypt_Blowfish-1.1.0_rc2-r1.ebuild
+++ b/dev-php/PEAR-Crypt_Blowfish/PEAR-Crypt_Blowfish-1.1.0_rc2-r1.ebuild
@@ -1,11 +1,11 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=5
inherit php-pear-r1
-DESCRIPTION="Allows for quick two-way Blowfish encryption without requiring the MCrypt PHP extension"
+DESCRIPTION="Quick, two-way Blowfish encryption without the MCrypt PHP extension"
LICENSE="BSD"
SLOT="0"
KEYWORDS="~amd64 ~x86"
next reply other threads:[~2017-07-10 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 3:16 Brian Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-19 15:04 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Crypt_Blowfish/ Brian Evans
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=1499655958.9d99d0c41b88c6c51730ad78c31e19790f2412ba.grknight@gentoo \
--to=grknight@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