Re: [fossil-users] Bug? FOSSIL MV does not work as expected (Win7 machine)

2015-04-21 Thread j. van den hoff
On Tue, 21 Apr 2015 11:09:05 +0200, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2015-04-21 10:24 GMT+02:00 Michael Richter ttmrich...@gmail.com: The key wording there is within the repository tree. It doesn't change the file system, only the naming of the files, etc. in the repository.

Re: [fossil-users] Bug? FOSSIL MV does not work as expected (Win7 machine)

2015-04-21 Thread Jan Nijtmans
2015-04-21 10:24 GMT+02:00 Michael Richter ttmrich...@gmail.com: The key wording there is within the repository tree. It doesn't change the file system, only the naming of the files, etc. in the repository. Whether this is desired or correct behaviour is … an area of frequent discussion.

Re: [fossil-users] Bug? FOSSIL MV does not work as expected (Win7 machine)

2015-04-21 Thread Michael Richter
The key wording there is *within the repository* tree. It doesn't change the file system, only the naming of the files, etc. in the repository. Whether this is desired or correct behaviour is … an area of frequent discussion. My own response to that discussion is to use the fsl wrapper (

[fossil-users] Bug? FOSSIL MV does not work as expected (Win7 machine)

2015-04-17 Thread Tony Papadimitriou
This is on a Win7 machine (if it matters). A simple way to reproduce (f = fossil): f new xxx.fossil f o xxx.fossil mkdir a\a dir a\a\xxx f add a f com -m Initial f mv a\a b f close Based on help screen, and usual behavior of mv, I would expect subdirectory a\a to be now known as b, and of