public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stephen Klimaszewski" <steev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/http-parser/
Date: Fri,  4 Mar 2016 03:28:30 +0000 (UTC)	[thread overview]
Message-ID: <1457062086.b3267726fd9756c9ac18d5c09c55dcb0a0d0df45.steev@gentoo> (raw)

commit:     b3267726fd9756c9ac18d5c09c55dcb0a0d0df45
Author:     Steev Klimaszewski <steev <AT> gentoo <DOT> org>
AuthorDate: Fri Mar  4 03:24:10 2016 +0000
Commit:     Stephen Klimaszewski <steev <AT> gentoo <DOT> org>
CommitDate: Fri Mar  4 03:28:06 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b3267726

net-libs/http-parser: Keyword 2.6.1 for ~arm64

Tested on Cortex-A53

Package-Manager: portage-2.2.27

 net-libs/http-parser/http-parser-2.6.1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net-libs/http-parser/http-parser-2.6.1.ebuild b/net-libs/http-parser/http-parser-2.6.1.ebuild
index bb8cbd2..ae7e9eb 100644
--- a/net-libs/http-parser/http-parser-2.6.1.ebuild
+++ b/net-libs/http-parser/http-parser-2.6.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/nodejs/http-parser/archive/v${PV}.tar.gz -> ${P}.tar
 
 LICENSE="MIT"
 SLOT="0/${PV}"
-KEYWORDS="~amd64 ~arm ~ppc ~x86 ~x64-macos ~x64-solaris"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~x86 ~x64-macos ~x64-solaris"
 IUSE="static-libs"
 
 # https://github.com/nodejs/http-parser/pull/272


             reply	other threads:[~2016-03-04  3:28 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  3:28 Stephen Klimaszewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-13 19:38 [gentoo-commits] repo/gentoo:master commit in: net-libs/http-parser/ Arthur Zamarin
2022-09-09  7:59 David Seifert
2021-07-24 23:02 Marek Szuba
2020-11-18  8:28 Michał Górny
2020-11-17 18:50 Agostino Sarubbo
2020-11-17 16:22 Michał Górny
2020-11-15  5:19 Sam James
2020-11-13  4:57 Sam James
2020-11-12 23:09 Thomas Deutschmann
2020-11-10 21:25 Sam James
2020-11-04 20:24 Sam James
2020-11-04  8:16 Sergei Trofimovich
2020-11-03 22:23 Michał Górny
2020-11-03 22:23 Michał Górny
2020-11-03 22:23 Michał Górny
2020-03-25  8:12 Agostino Sarubbo
2020-03-24 11:57 Jeroen Roovers
2020-03-22 11:58 Mart Raudsepp
2020-03-22 10:36 Agostino Sarubbo
2020-03-20 20:17 Thomas Deutschmann
2020-02-11 13:06 Agostino Sarubbo
2020-02-06  9:45 Jeroen Roovers
2019-11-19 10:36 Agostino Sarubbo
2019-11-11 17:59 Aaron Bauman
2019-11-01 21:03 Thomas Deutschmann
2019-05-27 21:04 Aaron Bauman
2019-04-16  9:47 Jeroen Roovers
2019-04-16  9:47 Jeroen Roovers
2019-04-11  6:17 Jeroen Roovers
2018-12-29 10:55 Jeroen Roovers
2018-12-28 10:53 Jeroen Roovers
2018-12-27 21:26 Jeroen Roovers
2018-12-12 13:04 Mikle Kolyada
2018-11-17 15:28 Mikle Kolyada
2018-10-05 15:13 Mikle Kolyada
2018-09-17 18:33 Matt Turner
2018-09-17 18:33 Matt Turner
2018-09-12 20:47 Thomas Deutschmann
2018-04-15 19:19 Jeroen Roovers
2018-04-15  9:48 Jeroen Roovers
2018-04-15  9:48 Jeroen Roovers
2018-04-15  8:55 Jeroen Roovers
2018-04-11  6:21 Jeroen Roovers
2018-02-24 10:54 Jeroen Roovers
2018-02-24 10:54 Jeroen Roovers
2017-10-30  0:01 Jonas Stein
2017-08-23  4:38 Tim Harder
2017-02-27 18:55 Michael Weber
2017-01-15  3:12 Göktürk Yüksek
2016-07-08  8:17 Agostino Sarubbo
2016-05-25 11:25 Agostino Sarubbo
2016-05-25  9:48 Agostino Sarubbo
2016-05-18  8:46 Fabian Groffen
2016-04-03 13:00 Jeroen Roovers
2016-03-09  7:01 Patrick Lauer
2016-02-10  8:01 Ian Delaney
2016-01-23 11:14 Fabian Groffen
2015-11-07 20:25 Julian Ospald

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=1457062086.b3267726fd9756c9ac18d5c09c55dcb0a0d0df45.steev@gentoo \
    --to=steev@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