Hello, I have been avoiding 'fossil mv' a bit until recently, because I didn't trust it for no good reason. I reckon since it is in trunk, it is considered stable.
In project-trees here, I move/rename dirs and files quite often. What I did earlier, was simply to move them as per filesystem, and then let 'fossil addremove' do its thing, and make a commit of only those additions/removals. I was wondering what you generally do for directory trees in motion - use add/rm or mv ? And: the benefit of fossil having a concept of 'moved file/dir' is that the user can trace ancestry crossing moves/renames more easily, is that correct? (At least that's how I use it now.) Michai _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
