docs: remove duplicated statements

The removed statement appears to express the same sentiment as bullet point 3 about rollbacks. Additionally, I removed the reference to issue #468; there doesn't appear to be an issue with that number. Signed-off-by: Micah Abbott <[email protected]>
containers · Mar 17, 2024 · ff19d23 · ff19d23
1 parent cc257ac
commit ff19d23
Showing 1 changed file with 1 addition and 3 deletions.
diff --git 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])