public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/i3status/
Date: Sat, 11 Feb 2023 00:36:25 +0000 (UTC)	[thread overview]
Message-ID: <1676075772.946d854632f2db973c9959812106f5789f8df8b0.sam@gentoo> (raw)

commit:     946d854632f2db973c9959812106f5789f8df8b0
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 11 00:28:56 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Feb 11 00:36:12 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=946d8546

x11-misc/i3status: fix filecaps desc. typo

Signed-off-by: Sam James <sam <AT> gentoo.org>

 x11-misc/i3status/metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-misc/i3status/metadata.xml b/x11-misc/i3status/metadata.xml
index b052e7bb4940..e16cefd50de7 100644
--- a/x11-misc/i3status/metadata.xml
+++ b/x11-misc/i3status/metadata.xml
@@ -14,7 +14,7 @@
 		your CPU as much as spawning the corresponding amount of shell commands would.
 	</longdescription>
 	<use>
-		<flag name="filecaps">Linux capabilities library is required for i3status to be able to read net bandwith</flag>
+		<flag name="filecaps">Linux capabilities library is required for i3status to be able to read net bandwidth</flag>
 	</use>
 	<upstream>
 		<remote-id type="github">i3/i3status</remote-id>


             reply	other threads:[~2023-02-11  0:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  0:36 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-20 12:02 [gentoo-commits] repo/gentoo:master commit in: x11-misc/i3status/ Jakov Smolić
2023-06-11 18:22 Andreas Sturmlechner
2023-06-11 18:22 Andreas Sturmlechner
2023-02-11  0:36 Sam James
2023-02-11  0:36 Sam James
2022-07-01  7:24 Arthur Zamarin
2021-11-22 14:01 Alexys Jacob
2021-09-21 13:41 Yixun Lan
2021-08-04 15:19 Alexys Jacob
2021-08-04  9:01 Sergei Trofimovich
2021-01-23 11:28 Sergei Trofimovich
2021-01-18  0:48 Sam James
2021-01-18  0:47 Sam James
2021-01-17 16:12 Jonas Stein
2020-11-26 22:30 Sergei Trofimovich
2020-11-26 22:15 Sergei Trofimovich
2020-11-25  7:45 Agostino Sarubbo
2020-11-25  7:43 Agostino Sarubbo
2019-07-05  8:36 Jeroen Roovers
2018-07-16  6:32 Johannes Huber
2018-07-15 16:33 Mikle Kolyada
2018-07-10 19:03 Johannes Huber
2018-05-25 18:20 Aaron Bauman
2018-05-13 16:18 Jeroen Roovers
2018-03-26 19:18 Aaron Bauman
2018-01-06 21:49 Markus Meier
2017-06-20 12:53 Pacho Ramos
2016-06-05 13:37 Lars Wendler
2016-01-06 14:49 Kacper Kowalik
2016-01-03  5:00 Kacper Kowalik

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=1676075772.946d854632f2db973c9959812106f5789f8df8b0.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