Renaming/moving files/folders/directories seems to work fine with the latest 0.11.5 release, but why are those file/folders/directories also put in the .stversions directory/folder? Yes it’s a change of location/name, so putting it there seems valid, but the file/folder remains the same. If I want to reorder my folder-structure/filenaming it means that I get everything double on the remote ends (with versioning on offcourse). Isn’t that a waste of space? Or am I just miss using synthing then?
That’s what I already mentioned
It’s probably like this because in the beginning there was nothing like a rename in syncthing, it was a delete on the source dir and a new file on the target dir. For versioning it looks like syncthing still handles it like this.
This could probably be fixed by replacing
archive here by something that moves the existing versions to the corresponding target in the version folder.
The file, under the name you knew it, is gone. An identical copy may exist somewhere else, but that’s slightly beside the point - especially as that copy may be modified in the near future, and you may not have been the one doing the rename to start with.
Or, shorter, meh. It could go either way, and this is one way to do it.
Hi, is there any way to archive that moved files are not copied to .stversions?
I want to archive that only deleted or maybe also renamed files will go to the .stversion folder.
As in my environment I have to move files often from one directory to another directory I don’t want to get a copy of the same in file each time I only move it to another location within the same folder created in .stversions.
I also checked the external version script option, but seems this will also not work as syncthing sees a move always as copy + delete of the file in the old location.
The above answer still stands.
I did not ask why, I asked if there is a way to get a different bahviour!
So I guess your answer means also: no there is no way.