From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-containers/docker/
Date: Sat, 27 May 2023 15:29:03 +0000 (UTC) [thread overview]
Message-ID: <1685201251.8f1e0d043022fa28b91f2581597e92151a5468f0.sam@gentoo> (raw)
commit: 8f1e0d043022fa28b91f2581597e92151a5468f0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat May 27 15:27:31 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat May 27 15:27:31 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8f1e0d04
app-containers/docker: fix UnusedLocalUse
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-containers/docker/metadata.xml | 6 ------
1 file changed, 6 deletions(-)
diff --git a/app-containers/docker/metadata.xml b/app-containers/docker/metadata.xml
index 5f163941881c..c8dfe231c86b 100644
--- a/app-containers/docker/metadata.xml
+++ b/app-containers/docker/metadata.xml
@@ -24,12 +24,6 @@
<flag name="btrfs">
Enables dependencies for the "btrfs" graph driver, including
necessary kernel flags.
- </flag>
- <flag name="cli">
- This is a temporary use flag which pulls in
- <pkg>app-containers/docker-cli</pkg>, the docker command line client.
- This flag is here to assist in the transition to split packages
- and will be removed in a future release.
</flag>
<flag name="container-init">
Makes the a staticly-linked init system tini available inside a
next reply other threads:[~2023-05-27 15:29 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 15:29 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-26 15:18 [gentoo-commits] repo/gentoo:master commit in: app-containers/docker/ William Hubbs
2025-07-04 19:15 Sam James
2025-06-22 15:37 Sam James
2025-06-22 14:50 Sam James
2025-06-05 21:31 William Hubbs
2025-04-22 18:58 William Hubbs
2025-04-11 14:35 William Hubbs
2025-03-16 22:05 William Hubbs
2025-03-16 10:19 Sam James
2025-03-16 6:27 Arthur Zamarin
2025-03-16 6:27 Arthur Zamarin
2025-03-05 17:50 William Hubbs
2025-02-26 21:43 William Hubbs
2025-01-28 14:52 William Hubbs
2025-01-15 14:08 William Hubbs
2025-01-14 7:25 Arthur Zamarin
2025-01-14 2:32 Sam James
2025-01-14 2:20 Sam James
2024-12-25 20:14 William Hubbs
2024-12-20 4:17 William Hubbs
2024-12-09 23:36 William Hubbs
2024-10-30 14:02 William Hubbs
2024-09-05 0:18 William Hubbs
2024-09-05 0:14 William Hubbs
2024-08-27 19:20 William Hubbs
2024-08-27 19:09 William Hubbs
2024-07-02 3:13 William Hubbs
2024-06-13 17:57 Sam James
2024-06-13 2:15 Sam James
2024-06-13 1:56 Sam James
2024-04-26 5:08 William Hubbs
2024-03-17 14:56 William Hubbs
2024-02-15 15:47 William Hubbs
2024-02-01 16:24 William Hubbs
2023-11-09 22:54 William Hubbs
2023-09-25 19:20 William Hubbs
2023-07-24 21:08 Sam James
2023-07-24 21:04 Sam James
2023-07-24 20:54 Sam James
2023-07-24 19:54 William Hubbs
2023-07-24 19:40 William Hubbs
2023-07-21 23:52 Sam James
2023-07-21 21:52 Sam James
2023-07-21 15:16 William Hubbs
2023-07-21 15:14 William Hubbs
2023-07-20 19:33 William Hubbs
2023-04-23 21:34 William Hubbs
2023-04-23 21:34 William Hubbs
2023-04-13 0:55 Sam James
2023-04-13 0:55 Sam James
2023-04-13 0:55 Sam James
2023-04-07 17:48 William Hubbs
2023-03-15 17:40 William Hubbs
2023-03-14 16:50 William Hubbs
2023-03-11 22:54 Sam James
2023-03-11 19:23 Sam James
2023-03-11 18:50 Sam James
2023-03-11 18:50 Sam James
2023-03-10 22:18 William Hubbs
2023-03-10 21:35 William Hubbs
2023-01-07 19:33 William Hubbs
2023-01-05 5:39 William Hubbs
2023-01-05 5:05 Sam James
2023-01-03 19:34 William Hubbs
2023-01-03 19:16 Arthur Zamarin
2023-01-03 16:04 William Hubbs
2022-08-20 22:09 William Hubbs
2022-08-19 19:33 Arthur Zamarin
2022-08-15 7:42 Agostino Sarubbo
2022-08-15 7:40 Agostino Sarubbo
2022-05-17 14:52 William Hubbs
2022-04-15 2:12 William Hubbs
2022-04-04 21:33 William Hubbs
2022-04-04 15:28 William Hubbs
2022-04-01 4:30 Sam James
2022-02-14 9:48 Jakov Smolić
2022-01-07 18:06 Georgy Yakovlev
2022-01-07 17:55 Georgy Yakovlev
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=1685201251.8f1e0d043022fa28b91f2581597e92151a5468f0.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