9/20/2023 0 Comments Allway sync vs. freefilesyncI spent ~15 minutes looking for this feature on the FFS GUI because I assumed it had what I thought was a basic feature of a program that is primarily used as sync/backup that supports versioning (in fact, I came across FFS when I was looking for a lightweight open source automated backup solution that supported versioning). Not the right thread for this but I though I would sneak it in.How about separate checkboxes on each folder pair to include/exclude syncing? I actually had to write my own program to clean up the old versioning folders. You mentioned that "Interestingly I hardly get any requests to implement a limit for versioning". I'm not yet sure how this could technically be done for naming convention "replace" with a versioning path like "C:\revisions\%timestamp%". Ideally a "limit" could be offered for both versioning naming conventions "replace" and "time stamp". I'm mentioning this because it might be necessary to limit the freedom of the versioning path in order to technically implement a limit. So apparently there's quite a lot right and very little wrong with the current design, therefore adding a limit of whatever kind must not break this advantage. by using macros like %timestamp% solved like 90% of the requirements of versioning. So it seems that giving users the freedom of using their own syntax for the versioning scheme e.g. Interestingly I hardly get any requests to implement a limit for versioning which is quite different compared to a few years back before I implemented the current versioning design. ![]() As always I'm trying to minimize the impact on the GUI and to avoid implementing features that hardly anyone wil be using (while FFS's future development could be constrained) I'm wondering if it would suffice to add a single option "keep last x days". “Retain those previous version younger than Y OR belonging to the latest X versions”: Variant B) can probably be referred to as the (logical) OR variant or as the MIN variant “Retain those previous version younger than Y AND belonging to the latest X versions” Variant A) can probably be referred to as the (logical) AND variant or as the MAX variant: Personally I would have a need for variant B), but I can imagine that the versioning options window would allow to choose not only the value of X and Y but also to choose between variant A) or B). * A number of previous versions (say: X), andīoth for X and Y, 0 (zero) could qualify as infinite (=no limit).īut how to combine the above? Variants are:Ī) Retain at most the latest X previous versions (if available) BUT ONLY those previous versions younger than Yī) Retain at least the latest X previous versions (if available) PLUS all/any other previous versions younger than Y To see that you are planning to (re-)introduce version limiting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |