public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-servers/caddy/
Date: Sat, 11 May 2024 15:16:34 +0000 (UTC)	[thread overview]
Message-ID: <1715440580.74e84fdbb1eba22cdf5dee8c79c0fce632c8a852.arthurzam@gentoo> (raw)

commit:     74e84fdbb1eba22cdf5dee8c79c0fce632c8a852
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat May 11 15:16:20 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat May 11 15:16:20 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=74e84fdb

www-servers/caddy: Stabilize 2.7.6-r2 amd64, #931746

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 www-servers/caddy/caddy-2.7.6-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www-servers/caddy/caddy-2.7.6-r2.ebuild b/www-servers/caddy/caddy-2.7.6-r2.ebuild
index 00c08cad4d9f..a6e09dd0ba77 100644
--- a/www-servers/caddy/caddy-2.7.6-r2.ebuild
+++ b/www-servers/caddy/caddy-2.7.6-r2.ebuild
@@ -17,7 +17,7 @@ else
 		https://dev.gentoo.org/~zmedico/dist/${PF}-deps.tar.xz
 		https://github.com/caddyserver/dist/archive/refs/tags/v${PV}.tar.gz -> ${P}-docs.tar.gz
 "
-	KEYWORDS="~amd64 ~arm64 ~loong ~riscv"
+	KEYWORDS="amd64 ~arm64 ~loong ~riscv"
 fi
 
 # MAIN


             reply	other threads:[~2024-05-11 15:16 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 15:16 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-01  1:47 [gentoo-commits] repo/gentoo:master commit in: www-servers/caddy/ Zac Medico
2024-06-29  3:15 Zac Medico
2024-06-29  3:15 Zac Medico
2024-06-29  3:15 Zac Medico
2024-06-16 23:07 Zac Medico
2024-05-13 12:37 Arthur Zamarin
2024-05-12 22:05 Zac Medico
2024-05-12 22:05 Zac Medico
2024-04-14 20:50 Zac Medico
2024-03-16 22:44 Zac Medico
2024-03-16 22:44 Zac Medico
2024-03-15 16:13 Arthur Zamarin
2024-03-15 15:37 Arthur Zamarin
2024-02-09  5:08 Zac Medico
2024-02-09  5:08 Zac Medico
2024-01-12  6:43 Joonas Niilola
2024-01-11 18:32 Sam James
2023-12-10 22:54 Zac Medico
2023-12-10 22:54 Zac Medico
2023-11-24 20:38 Sam James
2023-10-31 17:19 Mike Gilbert
2023-10-30  2:07 Zac Medico
2023-10-30  2:07 Zac Medico
2023-09-29  7:27 WANG Xuerui
2023-09-29  7:27 WANG Xuerui
2023-09-25  4:08 Zac Medico
2023-09-08 14:10 William Hubbs
2023-09-07 20:31 William Hubbs
2023-04-30 23:50 Sam James
2023-02-21  0:28 Zac Medico
2022-10-14  1:21 Zac Medico
2022-09-15  4:20 Zac Medico
2022-07-23  0:54 Zac Medico
2022-07-23  0:54 Zac Medico
2022-07-15 17:43 Zac Medico
2022-06-03  2:09 Zac Medico
2022-06-03  2:09 Zac Medico
2022-05-15 22:07 Zac Medico
2022-05-15 22:07 Zac Medico
2022-05-12  0:02 William Hubbs
2022-05-08 16:37 Zac Medico
2022-05-07 16:44 Zac Medico
2022-05-07 16:36 Zac Medico
2022-03-18  4:40 Zac Medico
2022-03-18  4:23 Zac Medico
2021-11-08 22:32 Zac Medico
2021-10-20  3:02 Zac Medico
2021-09-01 16:42 William Hubbs
2021-06-14 17:30 Zac Medico
2021-06-14 17:21 Zac Medico
2021-04-05 16:55 Zac Medico
2021-04-04 10:26 Zac Medico
2021-04-04 10:25 Zac Medico
2021-04-04 10:21 Zac Medico
2021-01-18  9:28 Joonas Niilola
2020-10-26 13:16 Joonas Niilola
2020-07-12 18:58 William Hubbs
2020-06-22 15:48 William Hubbs
2019-09-11 16:21 Michał Górny
2019-02-07 10:53 Manuel Rüger
2018-08-20 14:54 Manuel Rüger
2018-07-01 16:41 Sebastian Pipping
2018-02-21 14:33 Manuel Rüger
2018-02-21 14:33 Manuel Rüger
2017-10-09 14:07 Manuel Rüger
2017-09-18 11:08 Manuel Rüger
2017-09-14 13:14 Manuel Rüger
2017-09-10 10:49 Manuel Rüger
2017-09-08 22:02 Manuel Rüger
2017-08-12 12:25 Manuel Rüger
2017-08-01 12:31 Manuel Rüger
2017-08-01 12:30 Manuel Rüger
2017-07-19 14:56 Manuel Rüger
2017-05-16 20:34 Manuel Rüger
2017-04-21 15:03 Manuel Rüger
2017-03-13 15:49 Manuel Rüger

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=1715440580.74e84fdbb1eba22cdf5dee8c79c0fce632c8a852.arthurzam@gentoo \
    --to=arthurzam@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