From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/nghttp3/
Date: Tue, 18 Mar 2025 01:09:23 +0000 (UTC) [thread overview]
Message-ID: <1742260060.a8525b45a9ecabe139017b75b878a29bb7e5c5f4.sam@gentoo> (raw)
commit: a8525b45a9ecabe139017b75b878a29bb7e5c5f4
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 18 01:07:40 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Mar 18 01:07:40 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a8525b45
net-libs/nghttp3: Stabilize 1.8.0-r1 amd64, #951527
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-libs/nghttp3/nghttp3-1.8.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-libs/nghttp3/nghttp3-1.8.0-r1.ebuild b/net-libs/nghttp3/nghttp3-1.8.0-r1.ebuild
index 7ef62f198116..db66746f0312 100644
--- a/net-libs/nghttp3/nghttp3-1.8.0-r1.ebuild
+++ b/net-libs/nghttp3/nghttp3-1.8.0-r1.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} == 9999 ]] ; then
else
SRC_URI="https://github.com/ngtcp2/nghttp3/releases/download/v${PV}/${P}.tar.xz"
- KEYWORDS="~amd64 arm ~arm64 ~hppa ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86 ~arm64-macos ~x64-macos ~x64-solaris"
+ KEYWORDS="amd64 arm ~arm64 ~hppa ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86 ~arm64-macos ~x64-macos ~x64-solaris"
fi
DESCRIPTION="HTTP/3 library written in C"
next reply other threads:[~2025-03-18 1:09 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 1:09 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 1:13 [gentoo-commits] repo/gentoo:master commit in: net-libs/nghttp3/ Sam James
2025-03-18 1:13 Sam James
2025-03-18 1:13 Sam James
2025-03-18 1:09 Sam James
2025-03-18 1:09 Sam James
2025-03-18 1:09 Sam James
2025-03-18 1:09 Sam James
2025-03-18 1:09 Sam James
2025-03-18 0:57 Sam James
2025-03-18 0:31 Sam James
2025-03-18 0:28 Sam James
2025-02-21 15:45 Craig Andrews
2025-01-25 3:40 Matt Turner
2025-01-23 22:43 Sam James
2025-01-23 22:43 Sam James
2025-01-23 22:43 Sam James
2025-01-04 17:26 Sam James
2025-01-03 11:32 Sam James
2025-01-03 1:50 Sam James
2025-01-03 1:50 Sam James
2025-01-03 1:47 Sam James
2025-01-03 1:47 Sam James
2024-12-19 14:18 Craig Andrews
2024-11-10 17:06 James Le Cuirot
2024-10-30 22:09 Sam James
2024-10-13 19:27 Arthur Zamarin
2024-10-07 13:37 Craig Andrews
2024-10-04 17:30 Arthur Zamarin
2024-10-03 16:11 Arthur Zamarin
2024-10-03 1:00 Matt Jolly
2024-09-29 22:59 Sam James
2024-09-29 19:37 Sam James
2024-09-29 19:37 Sam James
2024-09-11 18:12 Arthur Zamarin
2024-08-29 5:16 Jakov Smolić
2024-08-26 8:00 Arthur Zamarin
2024-08-25 22:20 Craig Andrews
2024-08-20 8:20 Fabian Groffen
2024-08-20 7:22 WANG Xuerui
2024-08-20 7:22 WANG Xuerui
2024-08-14 1:38 Matt Jolly
2024-07-08 9:16 Matt Jolly
2024-07-08 9:16 Matt Jolly
2024-07-08 9:16 Matt Jolly
2024-06-13 14:01 Craig Andrews
2024-06-05 9:01 Yixun Lan
2024-06-01 6:22 Arthur Zamarin
2024-06-01 3:56 Sam James
2024-06-01 1:15 Sam James
2024-05-09 14:21 Craig Andrews
2024-04-05 15:26 Craig Andrews
2024-04-05 15:26 Craig Andrews
2024-04-05 15:08 Craig Andrews
2024-02-17 4:16 Craig Andrews
2023-11-26 15:35 Craig Andrews
2023-11-26 15:35 Craig Andrews
2023-10-16 12:47 Craig Andrews
2023-10-16 12:47 Craig Andrews
2023-09-05 12:53 Craig Andrews
2023-08-01 20:10 Craig Andrews
2023-07-20 21:04 Sam James
2023-07-10 13:50 Craig Andrews
2023-06-05 14:15 Craig Andrews
2023-04-26 14:32 Craig Andrews
2023-04-26 14:32 Craig Andrews
2023-03-27 13:38 Craig Andrews
2023-03-27 13:38 Craig Andrews
2023-02-24 14:51 Craig Andrews
2023-02-19 20:43 Craig Andrews
2023-02-19 20:43 Craig Andrews
2023-02-19 2:40 Craig Andrews
2019-10-08 15:16 Jeroen Roovers
2019-09-15 13:33 Craig Andrews
2019-09-15 0:34 Craig Andrews
2019-09-13 20:38 Craig Andrews
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=1742260060.a8525b45a9ecabe139017b75b878a29bb7e5c5f4.sam@gentoo \
--to=sam@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