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: net-proxy/tinyproxy/
Date: Thu, 29 Nov 2018 19:55:14 +0000 (UTC)	[thread overview]
Message-ID: <1543521299.3e753d244a6e249de5a2840c5f08ec2a8634d7f1.zlogene@gentoo> (raw)

commit:     3e753d244a6e249de5a2840c5f08ec2a8634d7f1
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 29 19:54:59 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Nov 29 19:54:59 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3e753d24

net-proxy/tinyproxy: amd64 stable wrt bug #626628

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11

 net-proxy/tinyproxy/tinyproxy-1.10.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-proxy/tinyproxy/tinyproxy-1.10.0-r1.ebuild b/net-proxy/tinyproxy/tinyproxy-1.10.0-r1.ebuild
index ecb2d43999b..3cf14c4a309 100644
--- a/net-proxy/tinyproxy/tinyproxy-1.10.0-r1.ebuild
+++ b/net-proxy/tinyproxy/tinyproxy-1.10.0-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/tinyproxy/tinyproxy/releases/download/${PV}/${P}.tar
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="alpha ~amd64 ~arm ia64 ppc ~sparc x86"
+KEYWORDS="alpha amd64 ~arm ia64 ppc ~sparc x86"
 
 IUSE="test debug +filter-proxy reverse-proxy transparent-proxy
 +upstream-proxy +xtinyproxy-header"


             reply	other threads:[~2018-11-29 19:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 19:55 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-01 17:03 [gentoo-commits] repo/gentoo:master commit in: net-proxy/tinyproxy/ Sam James
2024-07-01 17:03 Sam James
2024-07-01 16:58 Arthur Zamarin
2024-05-09 11:29 Ben Kohler
2023-03-30 18:05 Ben Kohler
2023-03-30 16:38 Sam James
2023-03-30 16:18 Arthur Zamarin
2023-03-30 15:34 Arthur Zamarin
2023-02-22 17:13 Ben Kohler
2023-01-10 16:11 Ben Kohler
2022-09-27 16:43 Ben Kohler
2022-09-27  7:10 Agostino Sarubbo
2022-09-27  7:08 Agostino Sarubbo
2022-09-27  6:05 Jakov Smolić
2022-09-20 12:02 Ben Kohler
2022-07-25 14:26 Ben Kohler
2022-07-20 13:31 Ben Kohler
2022-07-19 20:27 Sam James
2022-07-19 20:26 Sam James
2022-05-30 19:13 Ben Kohler
2021-05-18 11:56 Ben Kohler
2021-05-17 23:29 Sam James
2021-05-17 23:28 Sam James
2021-05-17 23:28 Sam James
2021-04-16 14:43 Ben Kohler
2021-01-05 14:56 Ben Kohler
2021-01-03 11:51 Sergei Trofimovich
2020-12-29 17:14 Sam James
2020-09-28 12:28 Ben Kohler
2020-09-06 12:35 Ben Kohler
2020-06-30 17:09 Ben Kohler
2018-11-30 17:43 Aaron Bauman
2018-11-28 22:33 Sergei Trofimovich
2018-11-28 22:28 Sergei Trofimovich
2018-11-27 21:55 Thomas Deutschmann
2018-11-27 16:01 Tobias Klausmann
2018-10-09 17:03 Ben Kohler
2018-10-09 13:26 Ben Kohler
2018-10-09 13:26 Ben Kohler
2018-10-09 13:21 Ben Kohler
2018-10-09 13:06 Ben Kohler
2016-05-04  9:35 Lars Wendler
2016-05-03 19:17 Austin English

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=1543521299.3e753d244a6e249de5a2840c5f08ec2a8634d7f1.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