public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/LWP-Protocol-https/
Date: Tue, 28 Sep 2021 13:59:25 +0000 (UTC)	[thread overview]
Message-ID: <1632837545.f045e6a32a0ae60ebb5b245e4388ca97304ca19a.chewi@gentoo> (raw)

commit:     f045e6a32a0ae60ebb5b245e4388ca97304ca19a
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 28 13:58:19 2021 +0000
Commit:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Tue Sep 28 13:59:05 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f045e6a3

dev-perl/LWP-Protocol-https: Keyword 6.100.0 for ~m68k

The tests pass.

Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>

 dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.100.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.100.0.ebuild b/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.100.0.ebuild
index e2fb78efd2d..d68788c5eba 100644
--- a/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.100.0.ebuild
+++ b/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.100.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="Provide https support for LWP::UserAgent"
 
 SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~x64-solaris"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~x64-solaris"
 
 RDEPEND="
 	app-misc/ca-certificates


             reply	other threads:[~2021-09-28 13:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 13:59 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-14  0:43 [gentoo-commits] repo/gentoo:master commit in: dev-perl/LWP-Protocol-https/ Sam James
2024-06-09 21:18 Sam James
2024-06-09 21:18 Sam James
2024-06-09 21:08 Sam James
2024-05-02  1:36 Sam James
2023-08-19  7:23 Sam James
2023-08-19  6:33 Sam James
2023-08-19  6:07 Sam James
2023-08-19  6:03 Sam James
2023-08-19  5:58 Sam James
2023-08-19  5:58 Sam James
2023-07-09 23:02 Sam James
2022-05-14  6:54 WANG Xuerui
2021-12-27 12:57 Fabian Groffen
2021-11-11 18:48 Andreas K. Hüttel
2021-08-06  0:30 Sam James
2021-08-03 12:38 Agostino Sarubbo
2021-08-03 10:54 Sam James
2021-08-02  4:56 Sam James
2021-08-02  2:19 Sam James
2021-08-01  7:24 Sam James
2021-06-26 21:47 Andreas K. Hüttel
2021-01-08 16:18 Fabian Groffen
2020-07-23 11:11 Kent Fredric
2020-07-18  7:04 Kent Fredric
2020-07-18  3:42 Kent Fredric
2019-05-04 18:53 Andreas K. Hüttel
2018-10-19 18:15 Fabian Groffen
2018-08-20  3:41 Mikle Kolyada
2018-07-23  0:33 Mikle Kolyada
2018-07-22  9:01 Sergei Trofimovich
2018-07-21 11:50 Tobias Klausmann
2018-07-20 22:48 Sergei Trofimovich
2018-07-20  8:08 Sergei Trofimovich
2018-07-16  6:54 Sergei Trofimovich
2018-07-15 23:57 Mikle Kolyada
2018-07-15 10:25 Sergei Trofimovich
2018-07-09 22:43 Mikle Kolyada
2018-02-24 21:19 Michał Górny
2017-11-09  0:49 Matt Turner
2017-10-16 21:27 Kent Fredric
2016-03-26 20:06 Andreas Hüttel
2016-03-26 15:22 Agostino Sarubbo

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=1632837545.f045e6a32a0ae60ebb5b245e4388ca97304ca19a.chewi@gentoo \
    --to=chewi@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