public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Conrad Kostecki" <conikost@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/dunst/
Date: Mon, 22 May 2023 21:35:59 +0000 (UTC)	[thread overview]
Message-ID: <1684791345.aff66aa2207273f26617e7ff97c994caadb45f6c.conikost@gentoo> (raw)

commit:     aff66aa2207273f26617e7ff97c994caadb45f6c
Author:     Conrad Kostecki <conikost <AT> gentoo <DOT> org>
AuthorDate: Mon May 22 21:28:18 2023 +0000
Commit:     Conrad Kostecki <conikost <AT> gentoo <DOT> org>
CommitDate: Mon May 22 21:35:45 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aff66aa2

x11-misc/dunst: amd64 stable

Signed-off-by: Conrad Kostecki <conikost <AT> gentoo.org>

 x11-misc/dunst/dunst-1.9.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-misc/dunst/dunst-1.9.2.ebuild b/x11-misc/dunst/dunst-1.9.2.ebuild
index 2414b563605b..5b1edf0ad638 100644
--- a/x11-misc/dunst/dunst-1.9.2.ebuild
+++ b/x11-misc/dunst/dunst-1.9.2.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/dunst-project/dunst/archive/v${PV}.tar.gz -> ${P}.ta
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~x86"
 IUSE="wayland"
 
 DEPEND="


             reply	other threads:[~2023-05-22 21:36 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 21:35 Conrad Kostecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-17 20:45 [gentoo-commits] repo/gentoo:master commit in: x11-misc/dunst/ Conrad Kostecki
2024-04-17 14:13 Conrad Kostecki
2024-04-17 11:39 Conrad Kostecki
2024-04-17 11:39 Conrad Kostecki
2024-04-17 11:39 Conrad Kostecki
2024-03-09 13:57 Conrad Kostecki
2024-03-09 13:57 Conrad Kostecki
2023-05-22 21:35 Conrad Kostecki
2023-04-22  0:11 Conrad Kostecki
2023-04-18 20:38 Conrad Kostecki
2023-04-18 20:38 Conrad Kostecki
2023-04-18 20:38 Conrad Kostecki
2023-03-12 19:00 Conrad Kostecki
2023-03-12 19:00 Conrad Kostecki
2022-07-29 19:06 Conrad Kostecki
2022-07-29 19:06 Conrad Kostecki
2022-07-29 19:06 Conrad Kostecki
2022-06-28 20:21 Conrad Kostecki
2022-04-01 22:55 Conrad Kostecki
2022-04-01 22:55 Conrad Kostecki
2022-04-01 22:55 Conrad Kostecki
2022-03-02 20:29 Conrad Kostecki
2022-03-02 20:29 Conrad Kostecki
2022-02-28  0:03 Conrad Kostecki
2022-02-25 11:34 Conrad Kostecki
2022-01-20 22:58 Conrad Kostecki
2022-01-20 22:58 Conrad Kostecki
2021-12-11  0:08 Conrad Kostecki
2021-12-11  0:08 Conrad Kostecki
2021-12-05 21:45 Conrad Kostecki
2021-12-05 21:45 Conrad Kostecki
2021-11-24 22:31 Conrad Kostecki
2021-11-24  8:05 Arthur Zamarin
2021-11-22 18:50 Arthur Zamarin
2021-11-22 18:50 Arthur Zamarin
2021-11-22  5:57 Yixun Lan
2021-11-21 14:41 Conrad Kostecki
2021-11-21 14:41 Conrad Kostecki
2021-11-21 14:41 Conrad Kostecki
2021-11-21 14:41 Conrad Kostecki
2021-07-16  9:51 Joonas Niilola
2021-07-16  9:51 Joonas Niilola
2021-05-14  0:38 Sam James
2021-05-14  0:38 Sam James
2021-04-29 11:43 Joonas Niilola
2021-04-29 11:43 Joonas Niilola
2021-04-29 11:43 Joonas Niilola
2021-03-04 17:42 Joonas Niilola
2020-09-05 10:49 Jeroen Roovers
2020-09-04  8:12 Jeroen Roovers
2020-01-23 10:25 Jeroen Roovers
2020-01-23 10:25 Jeroen Roovers
2020-01-23 10:25 Jeroen Roovers
2019-10-28 10:41 Jeroen Roovers
2019-10-07  3:51 Jeroen Roovers
2018-07-09 16:21 Johannes Huber
2018-07-09 15:14 Mikle Kolyada
2018-06-26 12:30 Johannes Huber
2018-05-23 18:38 Johannes Huber
2018-05-23 18:38 Johannes Huber
2018-05-23 18:38 Johannes Huber
2018-05-23 18:38 Johannes Huber
2017-09-09 12:32 Jeroen Roovers
2017-09-09 12:30 Jeroen Roovers
2017-08-24 20:36 Jeroen Roovers
2017-07-26 20:01 Markus Meier
2017-07-25  4:46 Jeroen Roovers
2017-07-25  4:46 Jeroen Roovers
2016-09-24 10:30 Jeroen Roovers
2016-08-07  6:52 Pacho Ramos
2016-06-06 13:33 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=1684791345.aff66aa2207273f26617e7ff97c994caadb45f6c.conikost@gentoo \
    --to=conikost@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