public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/kpeg/
Date: Sun, 18 Nov 2018 08:11:07 +0000 (UTC)	[thread overview]
Message-ID: <1542528496.4297c0c1273f6fac98fefab9d0d694cf15d6a3be.graaff@gentoo> (raw)

commit:     4297c0c1273f6fac98fefab9d0d694cf15d6a3be
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 18 07:46:49 2018 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Nov 18 08:08:16 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4297c0c1

dev-ruby/kpeg: amd64 stable

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11

 dev-ruby/kpeg/kpeg-1.1.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/kpeg/kpeg-1.1.0-r1.ebuild b/dev-ruby/kpeg/kpeg-1.1.0-r1.ebuild
index 0d98cd4bdf0..e6ab0b20f7a 100644
--- a/dev-ruby/kpeg/kpeg-1.1.0-r1.ebuild
+++ b/dev-ruby/kpeg/kpeg-1.1.0-r1.ebuild
@@ -13,7 +13,7 @@ HOMEPAGE="https://github.com/evanphx/kpeg"
 
 LICENSE="MIT"
 SLOT="1"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test"
 
 PATCHES=( "${FILESDIR}/${P}-utf8.patch" )


             reply	other threads:[~2018-11-18  8:11 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18  8:11 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-27 19:51 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/kpeg/ Hans de Graaff
2023-04-09 19:24 Arthur Zamarin
2023-04-08 11:13 Arthur Zamarin
2023-04-07  6:38 Sam James
2023-04-07  4:16 Sam James
2023-04-07  4:16 Sam James
2023-04-07  4:14 Sam James
2023-03-28 22:43 Sam James
2023-03-28 22:19 Sam James
2023-03-28 22:12 Sam James
2023-03-28 21:52 Sam James
2023-03-28 21:50 Sam James
2023-03-28 21:44 Sam James
2023-03-28 21:44 Sam James
2023-03-07  6:34 Hans de Graaff
2023-03-04 10:25 Hans de Graaff
2022-11-02  7:01 Hans de Graaff
2022-03-12  7:21 Hans de Graaff
2022-01-11  6:25 Hans de Graaff
2021-10-31  4:50 Hans de Graaff
2021-10-21  5:42 Hans de Graaff
2021-07-21 10:27 Marek Szuba
2020-12-28  7:46 Hans de Graaff
2019-12-26 11:06 Hans de Graaff
2019-06-24 15:14 Michael Haubenwallner
2019-04-27 19:48 Aaron Bauman
2018-12-30  3:43 Matt Turner
2018-12-27  2:57 Matt Turner
2018-12-26  8:20 Hans de Graaff
2018-12-25 11:11 Sergei Trofimovich
2018-12-15 14:25 Mikle Kolyada
2018-12-11 16:42 Thomas Deutschmann
2018-11-17 21:34 Thomas Deutschmann
2018-07-14  6:10 Hans de Graaff
2017-12-25 17:02 Hans de Graaff
2017-06-28  9:35 Alexis Ballier
2017-06-22 11:35 Fabian Groffen
2017-06-21 12:45 Fabian Groffen
2016-12-26 19:17 Hans de Graaff
2016-12-26  9:50 Hans de Graaff
2016-12-25  9:58 Hans de Graaff

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=1542528496.4297c0c1273f6fac98fefab9d0d694cf15d6a3be.graaff@gentoo \
    --to=graaff@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