Hi, I found an unexpected inconsistency with fossil mv on files when using wildcards.
I want to move 2 files into another directory: itest.asm and itest.bin Both files exist in the repository. If both exist locally: fossil mv itest.* newdir then fossil will rename *both*. changes show both have been renamed. If only itest.bin exists in the starting directory: fossil mv itest.* newdir will only rename itest.bin and not itest.asm I can still do this (including when itest.asm doesn't exist): fossil mv itest.asm newdir then fossil will rename the file regardless of it existing or not because fossil knows it exists in the repository. So wildcards appear to apply to the files locally rather than those in the repository. Should wildcards apply to both locally and in the repository? And this highlights another issue with the two step move: I can use fossil mv to move files but if I don't then move them locally then I can't submit and fossil reports it can't find the file. The process relies on both local moving of files and moving them in the repository. The operations have to be done in a specific order and are not independent. So my argument is that it should not be two step. It should be single step. Fossil already handles file operations so why is this different and why can't it be done automatically? (Sorry about the number of e-mails relating to mv, I'm re-organising files in my repository and I've e-mailed as I found these issues). Thanks Kevin _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
