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-cpp/gflags/
Date: Wed, 27 Nov 2019 13:16:23 +0000 (UTC)	[thread overview]
Message-ID: <1574860558.eda8264fb06812b7048acb9ec03c100a27ef2856.zlogene@gentoo> (raw)

commit:     eda8264fb06812b7048acb9ec03c100a27ef2856
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 27 13:15:58 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Wed Nov 27 13:15:58 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eda8264f

dev-cpp/gflags: arm stable wrt bug #700774

Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 dev-cpp/gflags/gflags-2.2.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-cpp/gflags/gflags-2.2.1-r1.ebuild b/dev-cpp/gflags/gflags-2.2.1-r1.ebuild
index 2dcc5901dc1..0bce0bfcd8d 100644
--- a/dev-cpp/gflags/gflags-2.2.1-r1.ebuild
+++ b/dev-cpp/gflags/gflags-2.2.1-r1.ebuild
@@ -10,7 +10,7 @@ if [[ ${PV} == 9999 ]]; then
 	EGIT_REPO_URI="https://github.com/gflags/gflags"
 else
 	SRC_URI="https://github.com/gflags/gflags/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-	KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh ~sparc x86 ~amd64-linux ~x86-linux"
+	KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh ~sparc x86 ~amd64-linux ~x86-linux"
 fi
 
 DESCRIPTION="Google's C++ argument parsing library"


             reply	other threads:[~2019-11-27 13:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 13:16 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-10 21:00 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/gflags/ Matt Turner
2023-07-10 21:00 Matt Turner
2023-07-10 21:00 Matt Turner
2023-03-22 18:53 Andreas Sturmlechner
2023-02-01 19:27 Andreas Sturmlechner
2022-08-04  8:04 Agostino Sarubbo
2022-08-03 17:30 Arthur Zamarin
2022-08-03  7:49 Agostino Sarubbo
2022-08-03  4:38 Arthur Zamarin
2022-08-03  4:38 Arthur Zamarin
2022-08-03  4:38 Arthur Zamarin
2022-08-03  4:38 Arthur Zamarin
2022-06-14  6:17 Jakov Smolić
2021-08-08 19:05 Amy Liffey
2021-03-06 12:24 Andreas Sturmlechner
2020-09-30  5:48 Andreas Sturmlechner
2019-11-23 16:49 Agostino Sarubbo
2019-11-23 15:46 Agostino Sarubbo
2019-11-23 12:43 Agostino Sarubbo
2019-11-23  2:36 Aaron Bauman
2019-11-22 10:24 Agostino Sarubbo
2019-07-06  6:17 Michał Górny
2019-05-16  3:54 Aaron Bauman
2018-01-04 21:05 Mikle Kolyada
2018-01-04  9:08 Mike Frysinger
2017-11-18 10:13 Sergei Trofimovich
2017-11-18 10:03 Sergei Trofimovich
2017-07-09 21:41 Michał Górny
2017-07-09 21:41 Michał Górny
2017-07-09 21:41 Michał Górny
2017-07-09 21:41 Michał Górny
2017-07-09 21:41 Michał Górny
2017-07-09 21:41 Michał Górny
2017-07-09 21:41 Michał Górny
2015-09-01 18:55 Tobias Klausmann

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=1574860558.eda8264fb06812b7048acb9ec03c100a27ef2856.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