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: dev-util/gtk-builder-convert/
Date: Sun,  6 Mar 2016 16:43:39 +0000 (UTC)	[thread overview]
Message-ID: <1457282413.552db05e099e292c635d370f98bf8d5d242a80a9.zlogene@gentoo> (raw)

commit:     552db05e099e292c635d370f98bf8d5d242a80a9
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Mar  6 16:30:23 2016 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Mar  6 16:40:13 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=552db05e

dev-util/gtk-builder-convert: x86 stable wrt bug #427546

Package-Manager: portage-2.2.26

 dev-util/gtk-builder-convert/gtk-builder-convert-2.24.29.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/gtk-builder-convert/gtk-builder-convert-2.24.29.ebuild b/dev-util/gtk-builder-convert/gtk-builder-convert-2.24.29.ebuild
index e61fe6c..d504234 100644
--- a/dev-util/gtk-builder-convert/gtk-builder-convert-2.24.29.ebuild
+++ b/dev-util/gtk-builder-convert/gtk-builder-convert-2.24.29.ebuild
@@ -14,7 +14,7 @@ HOMEPAGE="http://www.gtk.org/"
 
 LICENSE="LGPL-2+"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc ~x86 ~x86-fbsd ~x86-freebsd ~x86-interix ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc x86 ~x86-fbsd ~x86-freebsd ~x86-interix ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 
 IUSE=""
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"


             reply	other threads:[~2016-03-06 16:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 16:43 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-30  8:49 [gentoo-commits] repo/gentoo:master commit in: dev-util/gtk-builder-convert/ Pacho Ramos
2022-09-07  7:52 Michał Górny
2022-05-20 19:16 Pacho Ramos
2021-06-15 19:33 Matt Turner
2021-05-25 19:01 Matt Turner
2021-01-06 22:55 Fabian Groffen
2018-11-29 20:24 Mart Raudsepp
2018-11-25 10:03 Mikle Kolyada
2018-07-23 19:00 Sergei Trofimovich
2018-07-21  8:03 Tobias Klausmann
2018-07-14 20:16 Sergei Trofimovich
2018-07-14 20:10 Sergei Trofimovich
2018-07-09 16:14 Mikle Kolyada
2018-07-07 11:56 Sergei Trofimovich
2018-07-07  9:02 Sergei Trofimovich
2018-07-06 13:43 Thomas Deutschmann
2018-05-07  1:09 Mart Raudsepp
2017-08-26 10:07 Gilles Dartiguelongue
2017-08-26 10:07 Gilles Dartiguelongue
2017-03-16 13:24 Jeroen Roovers
2017-02-24 21:29 Michael Weber
2017-02-21  9:16 Tobias Klausmann
2017-02-18 14:44 Agostino Sarubbo
2016-12-06 20:26 Markus Meier
2016-11-01 17:31 Gilles Dartiguelongue
2016-09-17 13:32 Pacho Ramos
2016-09-17 13:32 Pacho Ramos
2016-07-30  9:34 Jeroen Roovers
2016-07-09 15:09 Pacho Ramos
2016-06-14 19:19 Pacho Ramos
2016-06-14 19:19 Pacho Ramos
2016-06-07  7:03 Tobias Klausmann
2016-05-03 20:12 Markus Meier
2015-12-12 14:29 Pacho Ramos
2015-12-12 14:29 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=1457282413.552db05e099e292c635d370f98bf8d5d242a80a9.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