Fossil SCM
Unexpected result moving directories with "fossil mv"
Open
9f0120fb739aa19…
· opened 15 years, 3 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Important
- Resolution
- Open
- Subsystem
- —
- Created
- Dec. 27, 2010 1:30 p.m.
When moving a directory with some contents, on the target the directory is lost. Let me illustrate with an example:
We have:
/a/f /a/b/ff
If I do:
$ mkdir c $ cd a $ fossil mv * ../c RENAME a/b/ff c/ff RENAME a/f c/f
So the tree structure is lost. Of course things get worse when ff and f have the same name, as then it results in an error because of the duplication.
Comments (1)
nobody
12 years, 9 months ago
I think this is basically the same bug (feature?):
fossil mv some_directory other_directory
Will move the contents of some_directory to other_directory instead of some_directory itself, which would be expected, as that is the behaviour of posix mv, that is it will act like one would expect from
fossil mv some_directory/* other_directory
which in turn would move the contents of the subdirectories of some_directory... you get the idea.