Overview
| Artifact ID: | e02bc5ee8493c06b29a36b08871dab87284059e8 |
|---|---|
| Ticket: | 7c3ca0eae8287e75f79fdb05f2ed4942dcd2c0a0
"not a ordinary file" errors in update command |
| User & Date: | anonymous 2010-02-25 07:46:27 |
Changes
- comment changed to:
With reference to ticket 15f8f4a425248c35fe0babfcb6ccf45f1d5b9932, the "not a ordinary file" problem is not restricted to the rm command. Attempting to do "fossil update" or "fossil checkout --latest" when any file has been deleted will cause a similar error. This change in behavior appears to remove all straightforward means of restoring deleted files; multiple commands or extra scripting will be needed if one wishes to restore several files. Not to mention that it breaks existing scripts written to automate fossil processes, for unclear reasons.
- foundin changed to: "20100213123048"
- private_contact changed to: "22e3b7a55e291d179313f4c2e34877f09743ee31"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to: ""not a ordinary file" errors in update command"
- type changed to: "Code_Defect"