Steve, I agree with you it is confusing! I have used fossil for over 2 years now (and I continue to use it because I like it very much) but I haven't used the move operation much in that time and each time I do use it the two step move is confusing.
I am used to other source control systems which move the files. I use them much more than I use fossil. I use fossil for my own personal code and the other scms for work. What confused me this time is that although technically it is true that the files are classed as MISSING after a move because fossil thinks they are in the new location , and the files have not been moved there, their status as MISSING should not be reported. If it remains as two step then saying their MISSING makes it sounds like something went wrong. Fossil should know it has moved/renamed the files as part of it's operation so if I do a mv command and then list changes, fossil should list them as RENAMED rather than MISSING. This would help. I think fossil should also remind the user to move the files if it's operating in two step mode. This would help me to remember each time ;) It's as simple as putting that in the changes and after the mv operation has been done-> "please don't forget to move your files". For changes, it could have 1 status for "renamed but file doesn't exist there yet" and "renamed and file exists" as a way to confirm to the user that they have done both operations. Also, if it is two step, then in theory I should be able to: 1. submit without moving files 2. do update to get the files in the new location. I am then free to delete the files in the original location the same way that I am free to copy the files or not. Also, what is confusing is what happens if there are changes to the files at the time of merge..? Of course not moving them is confusing for somebody like me who 1) doesn't use this method often 2) is used to the methods used by other scm makes it confusing each time. What also confused me is that when I did revert, fossil appeared to revert TWO operations (it listed the delete and revert). But changes only listed ONE operation. It seemed like the changes wasn't telling me all the information :( _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
