On 29 July 2015 at 16:50, Michai Ramakers <[email protected]> wrote: > Hello, > > using 'fossil mv' for the first time, and for some reason I don't > understand what happens here (see pasted output) - instead of renaming > a dir, it creates a zero-byte file (and leaves the original dir > as-is). > > I have the feeling I'm doing something really simple really wrong. Ideas..?
Right... creating the target-dir 'd2' beforehand worked in my case; any subdir existing under 'd' seems to be moved under 'd2' afterwards. Is it true what I wanted to do (rename a dir) needs to be a 2-step process, always? I thought that's exactly what '--hard' was meant to simplify. (I could rename the dir in the filesystem manually, and then use 'fossil mv' (without '--hard') to do the same thing, I think.) Then again, I didn't really follow the discussion about 'mv' semantics w.r.t. --hard and --soft and legacy behaviour a while ago. Michai _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
