| Ticket Hash: | 9f0120fb739aa19c3d4d84bf0fa5f289fd50d9c6 | ||
| Title: | Unexpected result moving directories with "fossil mv" | ||
| Status: | Open | Type: | Code_Defect |
| Severity: | Important | Priority: | |
| Subsystem: | Resolution: | Open | |
| Last Modified: |
2013-07-01 15:57:59 11.94 years ago |
Created: |
2010-12-27 13:30:51 14.45 years ago |
| Version Found In: | [0018d724b3] | ||
| Description: | ||||
|
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. | ||||
| User Comments: | ||||
|
nobody added on 2013-07-01 15:57:59:
I think this is basically the same bug (feature?): fossil mv some_directory other_directoryWill 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_directorywhich in turn would move the contents of the subdirectories of some_directory... you get the idea. | ||||