From 042e44cf817791e065611ee672f267377bd66e95 Mon Sep 17 00:00:00 2001 From: Micah Abbott Date: Fri, 15 Mar 2024 09:17:11 -0400 Subject: [PATCH] docs: remove duplicated statements The removed statement appears to express the same sentiment as bullet point 3 about rollbacks. Additionally, I included the correct link to the issue about the RPM limitation. Signed-off-by: Micah Abbott --- what-needs-work.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/what-needs-work.md b/what-needs-work.md index 2e2f3b7..82b6790 100644 --- a/what-needs-work.md +++ b/what-needs-work.md @@ -19,6 +19,4 @@ Broadly there are several areas where we haven’t yet reached our [goals](missi This would be confusing to a developer or someone trying to adopt these images. The behavior is different from the behavior of containers, where you can make changes to a running container, stop and start that container without losing those local changes. - * Currently when we deploy a bootable container image to a stock Linux system, without bootc already present, it is not possible to roll back. We should fix this. - - * Currently the tooling and the base images are limited to using RPM components in the container images. (bootc #468) + * Currently the tooling and the base images are limited to using RPM components in the container images. (See: [https://github.com/coreos/bootupd/issues/468])