If i understood "recorded timestamps" correctly, then /recorded/ means at the last real update a copy of the real time stamp is written to the local database state so it can be compared at a later time. For the unix file systems realized time stamping of creation, modification and access times the item in question is most probably the modification time. The Win32 platforms are using a very similar sheme for already a long time on many everyday file systems.
On Wednesday, January 23, 2019 at 4:25:41 PM UTC+1, Jens Wilhelm wrote: > > I think the description in > https://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-cleanup.html > under *Fix time stamps *is not correct. > As described in > https://subversion.apache.org/docs/api/latest/group__Cleanup.html the > meaning of this option is: > >> If *fix_recorded_timestamps* is TRUE, this function fixes recorded >> timestamps for unmodified files in the working copy, reducing comparision >> time on future checks. >> > This option doesn't change any timestamp of the files in the working copy. > It does change the entries in the pristine database instead. A changed > timestamp of an unchanged file will be stored into the field last_mod_time > in the NODES table. > In some cases this can has an effect to performance. > > > > > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/acbdae81-4040-4f1b-8a8f-6a9e035f2ae7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
