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-proxy/privoxy/
Date: Fri,  5 Feb 2016 19:07:23 +0000 (UTC)	[thread overview]
Message-ID: <1454699227.168120d13c062e0980363970a4d4e01c63b15570.maekke@gentoo> (raw)

commit:     168120d13c062e0980363970a4d4e01c63b15570
Author:     Markus Meier <maekke <AT> gentoo <DOT> org>
AuthorDate: Fri Feb  5 19:07:07 2016 +0000
Commit:     Markus Meier <maekke <AT> gentoo <DOT> org>
CommitDate: Fri Feb  5 19:07:07 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=168120d1

net-proxy/privoxy: arm stable, bug #572584

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

 net-proxy/privoxy/privoxy-3.0.24.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-proxy/privoxy/privoxy-3.0.24.ebuild b/net-proxy/privoxy/privoxy-3.0.24.ebuild
index c6d6f09..74acaee 100644
--- a/net-proxy/privoxy/privoxy-3.0.24.ebuild
+++ b/net-proxy/privoxy/privoxy-3.0.24.ebuild
@@ -18,7 +18,7 @@ IUSE="+acl editor external-filters +fast-redirects +force graceful-termination
 +image-blocking ipv6 lfs png-images selinux +stats +threads toggle
 whitelists +zlib"
 SLOT="0"
-KEYWORDS="alpha amd64 ~arm ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd"
+KEYWORDS="alpha amd64 arm ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd"
 LICENSE="GPL-2"
 
 DEPEND="dev-libs/libpcre


             reply	other threads:[~2016-02-05 19:07 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 19:07 Markus Meier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-11 11:35 [gentoo-commits] repo/gentoo:master commit in: net-proxy/privoxy/ Jakov Smolić
2024-07-11  6:22 Arthur Zamarin
2024-07-11  6:22 Arthur Zamarin
2024-07-11  6:22 Arthur Zamarin
2024-07-11  6:22 Arthur Zamarin
2024-07-11  6:22 Arthur Zamarin
2024-04-10 13:38 Yixun Lan
2024-04-10 13:38 Yixun Lan
2022-03-03  6:34 Yixun Lan
2022-01-04  3:29 Sam James
2021-12-26 12:20 Andrew Savchenko
2021-12-24  4:56 Sam James
2021-12-24  4:56 Sam James
2021-12-24  4:56 Sam James
2021-12-24  4:55 Sam James
2021-12-24  4:54 Sam James
2021-12-24  4:54 Sam James
2021-06-22 18:19 Sam James
2021-03-08 10:26 Sam James
2021-03-08 10:25 Sam James
2021-03-08  2:54 John Helmert III
2021-03-07 23:06 Sam James
2021-03-07 23:05 Sam James
2021-03-07 18:45 Sergei Trofimovich
2021-02-13 18:22 Sam James
2021-02-11  7:45 Sergei Trofimovich
2021-02-09 22:53 Sam James
2021-02-08 17:26 Sam James
2021-02-08 17:25 Sam James
2021-02-08 15:08 Sergei Trofimovich
2021-01-31  3:22 Andrew Savchenko
2021-01-26 17:42 Sergei Trofimovich
2021-01-24 22:45 Sam James
2021-01-24 22:07 Sam James
2021-01-24 21:52 Sam James
2021-01-24 21:51 Sam James
2021-01-07 15:30 Andrew Savchenko
2021-01-06  3:17 Andrew Savchenko
2020-09-07  8:47 Sergei Trofimovich
2020-09-07  8:20 Sergei Trofimovich
2020-08-28 22:21 Sergei Trofimovich
2020-08-25  0:11 Sam James
2020-08-22 11:26 Agostino Sarubbo
2020-08-22  5:50 Agostino Sarubbo
2020-08-21 15:27 Agostino Sarubbo
2020-08-19 11:06 Andrew Savchenko
2020-07-12  8:21 Andrew Savchenko
2020-07-12  8:21 Andrew Savchenko
2020-07-11 10:03 Andrew Savchenko
2020-07-11 10:03 Andrew Savchenko
2019-03-09 21:29 Andrew Savchenko
2017-07-09  1:05 Andrew Savchenko
2017-06-21 11:57 Agostino Sarubbo
2017-06-15 16:06 Markus Meier
2017-06-13 12:31 Agostino Sarubbo
2017-06-10 13:45 Agostino Sarubbo
2017-06-05 18:04 Thomas Deutschmann
2017-06-05 11:05 Agostino Sarubbo
2017-02-18 18:58 Markus Meier
2017-01-16 19:56 Tobias Klausmann
2017-01-10 14:56 Agostino Sarubbo
2017-01-10 11:26 Andrew Savchenko
2016-04-13 11:02 Andrew Savchenko
2016-03-19 13:30 Andrew Savchenko
2016-02-13  9:51 Jeroen Roovers
2016-02-04 10:51 Tobias Klausmann
2016-02-04 10:46 Agostino Sarubbo
2016-01-22 18:04 Andrew Savchenko
2016-01-22 18:04 Andrew Savchenko

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=1454699227.168120d13c062e0980363970a4d4e01c63b15570.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