public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-shells/nushell/
Date: Sun, 20 Jun 2021 21:34:31 +0000 (UTC)	[thread overview]
Message-ID: <1624224532.e99179b0d6bab2caac74e4c0f1ac8c912db12be4.gyakovlev@gentoo> (raw)

commit:     e99179b0d6bab2caac74e4c0f1ac8c912db12be4
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 20 21:28:52 2021 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Sun Jun 20 21:28:52 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e99179b0

app-shells/nushell: fix whitespace in metadata.xml

Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 app-shells/nushell/metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-shells/nushell/metadata.xml b/app-shells/nushell/metadata.xml
index 6d87ea0cbaf..152a432659c 100644
--- a/app-shells/nushell/metadata.xml
+++ b/app-shells/nushell/metadata.xml
@@ -11,7 +11,7 @@
 		<doc>https://www.nushell.sh/book/</doc>
 		<remote-id type="github">nushell/nushell</remote-id>
 	</upstream>
-    <use>
+	<use>
 		<flag name="extra">Install extra plugins: binaryview, tree, clipboard-cli, trash-support and others</flag>
 	</use>
 </pkgmetadata>


             reply	other threads:[~2021-06-20 21:34 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20 21:34 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-22  4:34 [gentoo-commits] repo/gentoo:master commit in: app-shells/nushell/ Sam James
2025-03-19 22:26 Zac Medico
2025-03-19 22:26 Zac Medico
2025-02-07 17:50 Sam James
2025-02-07  4:21 Zac Medico
2025-02-07  4:21 Zac Medico
2025-01-11 18:22 Zac Medico
2024-12-31  4:57 Sam James
2024-12-29 19:40 Zac Medico
2024-11-17 19:19 Zac Medico
2024-11-16  2:36 Zac Medico
2024-11-16  2:36 Zac Medico
2024-11-10 17:40 Zac Medico
2024-11-10 17:40 Zac Medico
2024-09-22 18:38 Arthur Zamarin
2024-09-21  8:58 Michał Górny
2024-09-20 15:32 Arthur Zamarin
2024-09-20 14:50 Arthur Zamarin
2024-09-20 14:50 Arthur Zamarin
2024-08-07  2:26 Zac Medico
2024-08-07  2:26 Zac Medico
2024-08-06 10:59 Sam James
2024-06-04 16:27 Zac Medico
2024-05-25  5:05 Arthur Zamarin
2024-05-19  8:43 Zac Medico
2024-04-16  5:42 Joonas Niilola
2024-04-16  5:42 Joonas Niilola
2024-04-05 16:40 Arthur Zamarin
2024-03-15  3:40 Zac Medico
2024-03-15  3:40 Zac Medico
2024-02-28  9:12 Florian Schmaus
2024-01-17  5:05 Zac Medico
2024-01-17  5:05 Zac Medico
2023-12-18  9:23 Zac Medico
2023-12-18  9:23 Zac Medico
2023-12-18  9:23 Zac Medico
2023-11-18  3:21 Zac Medico
2023-11-17 12:07 Sam James
2023-10-10 18:38 Florian Schmaus
2023-10-10 18:38 Florian Schmaus
2023-08-28  4:06 Zac Medico
2023-08-28  4:06 Zac Medico
2023-08-16  5:15 Zac Medico
2023-08-16  5:15 Zac Medico
2023-07-27  6:35 Zac Medico
2023-07-27  6:35 Zac Medico
2023-07-13  6:03 Zac Medico
2023-07-13  6:03 Zac Medico
2023-07-13  6:03 Zac Medico
2023-04-15  2:40 Sam James
2023-02-01  2:44 Zac Medico
2023-01-31  2:10 Zac Medico
2023-01-31  2:10 Zac Medico
2022-11-16  2:49 Zac Medico
2022-10-20  4:16 Zac Medico
2022-10-20  4:15 Zac Medico
2022-10-18  3:50 Zac Medico
2022-08-06 18:42 Zac Medico
2022-08-06 17:38 Zac Medico
2022-07-10 22:31 Zac Medico
2022-06-18 21:50 Zac Medico
2022-06-18 21:50 Zac Medico
2022-05-22 15:09 Zac Medico
2022-05-04  3:18 Zac Medico
2022-04-13  3:58 Zac Medico
2022-03-24  3:34 Zac Medico
2022-03-24  2:35 Zac Medico
2022-01-24  3:52 Zac Medico
2021-12-28 21:13 Zac Medico
2021-12-28 21:13 Zac Medico
2021-12-12 14:23 Yixun Lan
2021-12-08  4:11 Zac Medico
2021-11-17  1:34 Zac Medico
2021-10-31  5:23 Zac Medico
2021-06-20 21:34 Georgy Yakovlev
2021-06-20  8:45 Georgy Yakovlev
2021-06-20  6:36 Zac Medico

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=1624224532.e99179b0d6bab2caac74e4c0f1ac8c912db12be4.gyakovlev@gentoo \
    --to=gyakovlev@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