public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Markus Meier" <maekke@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/tor/
Date: Thu, 10 Nov 2016 17:47:13 +0000 (UTC)	[thread overview]
Message-ID: <1478800021.452f4072193ec4b0f058a9847ac864edf93b5abd.maekke@gentoo> (raw)

commit:     452f4072193ec4b0f058a9847ac864edf93b5abd
Author:     Markus Meier <maekke <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 10 17:47:01 2016 +0000
Commit:     Markus Meier <maekke <AT> gentoo <DOT> org>
CommitDate: Thu Nov 10 17:47:01 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=452f4072

net-misc/tor: arm stable, bug #597394

Package-Manager: portage-2.3.2
RepoMan-Options: --include-arches="arm"

 net-misc/tor/tor-0.2.8.9.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-misc/tor/tor-0.2.8.9.ebuild b/net-misc/tor/tor-0.2.8.9.ebuild
index fd16f3a..273a2e5 100644
--- a/net-misc/tor/tor-0.2.8.9.ebuild
+++ b/net-misc/tor/tor-0.2.8.9.ebuild
@@ -16,7 +16,7 @@ S="${WORKDIR}/${MY_PF}"
 
 LICENSE="BSD GPL-2"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~mips ~ppc ppc64 ~sparc x86 ~ppc-macos"
+KEYWORDS="amd64 arm ~mips ~ppc ppc64 ~sparc x86 ~ppc-macos"
 IUSE="-bufferevents libressl scrypt seccomp selinux stats systemd tor-hardening transparent-proxy test web"
 
 DEPEND="


             reply	other threads:[~2016-11-10 17:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 17:47 Markus Meier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-02 11:32 [gentoo-commits] repo/gentoo:master commit in: net-misc/tor/ Anthony G. Basile
2017-02-05  1:25 Anthony G. Basile
2017-01-25 16:21 Anthony G. Basile
2017-01-25 15:42 Anthony G. Basile
2017-01-25 15:42 Anthony G. Basile
2017-01-16 15:39 Jeroen Roovers
2017-01-08 18:34 Markus Meier
2017-01-05 14:02 Anthony G. Basile
2017-01-04 17:09 Agostino Sarubbo
2017-01-01 22:40 Agostino Sarubbo
2016-12-20  9:23 Anthony G. Basile
2016-12-20  9:23 Anthony G. Basile
2016-12-20  9:23 Anthony G. Basile
2016-12-10 18:53 Anthony G. Basile
2016-12-05 22:40 Anthony G. Basile
2016-11-28  1:58 Anthony G. Basile
2016-11-09  3:32 Anthony G. Basile
2016-11-05  9:55 Jeroen Roovers
2016-10-26  8:01 Michael Palimaka
2016-10-17 23:41 Anthony G. Basile
2016-09-23 21:07 Anthony G. Basile
2016-09-23 21:07 Anthony G. Basile
2016-08-24 19:07 Anthony G. Basile
2016-08-09  7:53 Anthony G. Basile
2016-08-03  8:22 Anthony G. Basile
2016-07-07 17:59 Anthony G. Basile
2016-06-15 18:49 Anthony G. Basile
2016-06-15 18:49 Anthony G. Basile
2016-05-27  8:50 Anthony G. Basile
2016-03-28 23:16 Anthony G. Basile
2016-03-28 23:16 Anthony G. Basile
2016-03-13 12:06 Anthony G. Basile
2016-02-05 22:52 Anthony G. Basile
2016-02-05 20:46 Anthony G. Basile
2016-01-23 14:49 Markus Meier
2016-01-15  9:03 Agostino Sarubbo
2015-12-11 12:57 Anthony G. Basile
2015-12-11  9:39 Anthony G. Basile
2015-11-21  0:38 Anthony G. Basile
2015-11-21  0:38 Anthony G. Basile
2015-11-09 19:02 Fabian Groffen
2015-10-22  1:20 Anthony G. Basile
2015-10-17  0:36 Anthony G. Basile
2015-10-16  5:05 Anthony G. Basile
2015-10-05  9:17 Julian Ospald
2015-09-26 10:26 Anthony G. Basile

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=1478800021.452f4072193ec4b0f058a9847ac864edf93b5abd.maekke@gentoo \
    --to=maekke@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