aef81bf344 2008-12-21    kejoki: <h2>mv | rename</h2>
aef81bf344 2008-12-21    kejoki: 
aef81bf344 2008-12-21    kejoki: The <code>mv</code> (alias "<code>rename</code>") command tells
aef81bf344 2008-12-21    kejoki: <b>fossil</b> that a file has gone from one external name to another
aef81bf344 2008-12-21    kejoki: without changing content.
aef81bf344 2008-12-21    kejoki: 
aef81bf344 2008-12-21    kejoki: You could do this by renaming the file in the file system,
aef81bf344 2008-12-21    kejoki: [./cmd_rm.wiki | deleting] the old name from the project, and
aef81bf344 2008-12-21    kejoki: [./cmd_add.wiki | adding] the new name.  But you would lose the
aef81bf344 2008-12-21    kejoki: continuity of the <u>content's</u> history that way.  Using
aef81bf344 2008-12-21    kejoki: <code>mv</code> makes the name change a part of the history
aef81bf344 2008-12-21    kejoki: maintained by <b>fossil</b>.  You will, of course, need a good
aef81bf344 2008-12-21    kejoki: comment somewhere (say, the commit comment) if you want to
aef81bf344 2008-12-21    kejoki: remember <em>why</em> you changed the name...  <b>fossil</b>
aef81bf344 2008-12-21    kejoki: only maintains history, it doesn't (yet) explain it.
aef81bf344 2008-12-21    kejoki: 
aef81bf344 2008-12-21    kejoki: <code>mv</code> is much like the [./cmd_rm.wiki | <code>rm</code>]
aef81bf344 2008-12-21    kejoki: command, in that it manipulates <b>fossil</b>'s "idea" of what is
aef81bf344 2008-12-21    kejoki: part of the project.  The difference is that <code>mv</code> assumes
aef81bf344 2008-12-21    kejoki: you have actually made some change to the file system.
aef81bf344 2008-12-21    kejoki: 
aef81bf344 2008-12-21    kejoki: See also: [./cmd_rm.wiki | fossil rm],
aef81bf344 2008-12-21    kejoki: [./cmd_add.wiki | fossil add],
aef81bf344 2008-12-21    kejoki: [./reference.wiki | Reference]