When using filestamp-renaming versioning, the program uses the time of current operation.
I'd like to suggest to use the file's own last-changed-timestamp for the renaming instead.
Thanks!
Search found 3 matches
- 09 Nov 2017, 19:24
- Forum: General Discussion
- Topic: feature request: timestamp versioning should reflect the file's time
- Replies: 2
- Views: 466
- 09 Nov 2017, 19:14
- Forum: General Discussion
- Topic: bug report: custom sync options
- Replies: 1
- Views: 435
bug report: custom sync options
I've noticed the following unexpected behaviour:
When using custom sync and altering the "conflicts" setting to either "rightwards" or "leftwards", the resulting action is always "leftwards."
using v9.5
If you can reproduce it then maybe one could call it a bug.
Thanks for your effort, great ...
When using custom sync and altering the "conflicts" setting to either "rightwards" or "leftwards", the resulting action is always "leftwards."
using v9.5
If you can reproduce it then maybe one could call it a bug.
Thanks for your effort, great ...
- 09 Nov 2017, 14:46
- Forum: Help
- Topic: Howto Handle Conflicts
- Replies: 9
- Views: 3821
Re: Howto Handle Conflicts
Hi, using v9.5 I managed conflict handling this way (requires 3 steps):
1. run 2way-default: conflicts=skip > syncs all non conflicting files
2. run 2way-custom: conflicts=leftwards & deletions=timestamp-versioning into left org folder(!) > forces sync and thereby renames conflicting files instead ...
1. run 2way-default: conflicts=skip > syncs all non conflicting files
2. run 2way-custom: conflicts=leftwards & deletions=timestamp-versioning into left org folder(!) > forces sync and thereby renames conflicting files instead ...