Overview
| Artifact ID: | 5b87d849781796dc1c8699b20d3ddb9b129ad7b0 |
|---|---|
| Ticket: | b081e09e28176eefdfd3a8a99d0d086205e890f0
On conflict of binary files locally, fossil overwrites local changes |
| User & Date: | anonymous 2011-01-26 22:25:20 |
Changes
- comment changed to:
In case of a modified binary file, and a later "fossil update" taking in changes in that file, fossil will overwrite the local file with that incoming. It will report CONFLICT on that file, leaving "fossil undo" as the only option to get the local changes back. A user may loose changes in that situation, if he fails to see the CONFLICT message. I think that fossil should, like subversion, copy the file with local changes into another filename in the same directory, like "myfile.odt~local".
- foundin changed to: "[6f42e76d80]"
- private_contact changed to: "ccd87c60364e1d3e945b6f4d4874f5174b17cc43"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to:
On conflict of binary files locally, fossil overwrites local changes
- type changed to: "Code_Defect"