Overview
Artifact ID: | 8d20eb300d217371c0d15d441cd81a73ae4d7c49 |
---|---|
Ticket: | 60211effbd2c6e3f823b4fadbbe9b29e1cc12a10
fossil mv nonexistentfile newfilename |
User & Date: | dmitry 2011-10-24 18:15:59 |
Changes
- Appended to comment:
<hr /><i>dmitry added on 2011-10-24 18:15:59 UTC:</i><br /> I think leaving it as is, issuing a warning, or asking a user to confirm the action instead of failing is better, because I sometimes first do <verbatim> mv file renamedfile </verbatim> and then remember to mv it in Fossil: <verbatim> fossil mv file renamedfile </verbatim> If Fossil didn't allow this, I'd have to rename the file back to the original name, then do `fossil mv`, and rename it again.
- resolution changed to: "Open"