chiark / gitweb /
README.md: Clarify dirtying bug
authorIan Jackson <ijackson@chiark.greenend.org.uk>
Fri, 19 Jun 2020 10:51:44 +0000 (11:51 +0100)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Fri, 19 Jun 2020 10:51:44 +0000 (11:51 +0100)
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
README.md

index 9891e08313c7f0028205ff44bf74e686712199f2..bd1581f5f1fa972328d35995e4e1f20ae2f9ef7e 100644 (file)
--- a/README.md
+++ b/README.md
@@ -296,12 +296,13 @@ Limitations and bugs
 ====================
 
   * nailing-cargo temporarily dirties your source trees, including
-    particularly `Cargo.toml` and `Cargo.lock`.  If nailing-cargo
-    crashes or is interrupted these changes may be left behind;
-    running nailing-cargo again should clean up such a mess.
-    Unfortunately it is not possible to fix this bug because the cargo
-    team have deliberately made cargo inflexible -
-    [issue#6715](https://github.com/rust-lang/cargo/issues/6715).
+    particularly `Cargo.toml` and `Cargo.lock`; and if nailing-cargo
+    crashes or is interrupted these changes may be left behind.
+    Unfortunately it is not possible to avoid this temporary dirtying
+    because the cargo team have deliberately made cargo inflexible -
+    [issue#6715](https://github.com/rust-lang/cargo/issues/6715).  
+    At least, running nailing-cargo again will clean up any mess
+    left by an interrupted run.
 
   * Out of tree builds require a unified filesystem view: eg, different
     users on the same host, NFS, or something.  This could be improved.