public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-arcade/gnome-nibbles/
Date: Thu, 18 Jan 2018 02:27:07 +0000 (UTC)	[thread overview]
Message-ID: <1516242227.a943aa11a8e5a44c3d20a04cd247350d12811629.zlogene@gentoo> (raw)

commit:     a943aa11a8e5a44c3d20a04cd247350d12811629
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 18 02:23:47 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Jan 18 02:23:47 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a943aa11

games-arcade/gnome-nibbles: amd64 stable wrt bug #631656

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 games-arcade/gnome-nibbles/gnome-nibbles-3.24.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/games-arcade/gnome-nibbles/gnome-nibbles-3.24.0.ebuild b/games-arcade/gnome-nibbles/gnome-nibbles-3.24.0.ebuild
index 405c8a5fdd5..e5c666e0265 100644
--- a/games-arcade/gnome-nibbles/gnome-nibbles-3.24.0.ebuild
+++ b/games-arcade/gnome-nibbles/gnome-nibbles-3.24.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -11,7 +11,7 @@ HOMEPAGE="https://wiki.gnome.org/Apps/Nibbles"
 
 LICENSE="GPL-3+ CC-BY-SA-3.0"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 IUSE=""
 
 RDEPEND="


             reply	other threads:[~2018-01-18  2:27 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  2:27 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-15 17:34 [gentoo-commits] repo/gentoo:master commit in: games-arcade/gnome-nibbles/ Pacho Ramos
2025-01-15 17:34 Pacho Ramos
2025-01-15 17:34 Pacho Ramos
2024-04-20 14:36 Mart Raudsepp
2024-04-13 10:37 Mart Raudsepp
2024-04-07 10:11 Arthur Zamarin
2024-04-07  5:55 Arthur Zamarin
2024-04-07  5:55 Arthur Zamarin
2024-03-02 22:33 Mart Raudsepp
2024-02-18  6:09 Arthur Zamarin
2024-02-09 22:26 Mart Raudsepp
2023-12-21  0:07 Ionen Wolkens
2023-12-20  9:58 Pacho Ramos
2023-12-20  9:58 Pacho Ramos
2023-12-20  9:58 Pacho Ramos
2023-06-17 17:09 Arthur Zamarin
2023-06-17 17:09 Arthur Zamarin
2023-06-03  5:24 Jakov Smolić
2023-05-01 18:16 Matt Turner
2022-10-30 15:42 Matt Turner
2022-09-15 21:00 Matt Turner
2022-02-08  4:45 Sam James
2021-04-24 10:43 Mart Raudsepp
2021-04-24  9:20 Mart Raudsepp
2021-03-21 22:00 Matt Turner
2020-08-22  7:21 Mart Raudsepp
2020-04-20 20:30 Mart Raudsepp
2019-12-22 20:47 Mart Raudsepp
2019-08-06  5:20 Mart Raudsepp
2019-08-04 22:35 Aaron Bauman
2018-09-14  8:17 Mart Raudsepp
2018-08-22 21:38 Mart Raudsepp
2018-02-03 19:40 Mart Raudsepp
2018-01-27  0:41 Thomas Deutschmann
2017-08-08 22:10 Gilles Dartiguelongue
2017-05-01 21:49 Mart Raudsepp
2016-12-06  9:33 Pacho Ramos
2016-11-09  8:28 Gilles Dartiguelongue
2016-10-30 11:44 Gilles Dartiguelongue
2016-09-04 23:20 Gilles Dartiguelongue
2016-07-02 10:43 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-03-06 16:43 Mikle Kolyada
2015-11-09 21:51 Pacho Ramos
2015-11-09 21:51 Pacho Ramos

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=1516242227.a943aa11a8e5a44c3d20a04cd247350d12811629.zlogene@gentoo \
    --to=zlogene@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