oHenri
Thank you. Yes, exactly this discussion on stack overflow I meant with "I read in some discussions that ..." But at most, it does not help me, because most of answers are out of TO's question. Anyway, for me it is essential too to preserve the original file modification date. Checkin time, ceckout time, all of that is - on level of file - not of interest for me. And most of non-svn tools like comparers etc do use the files modification date. Content comparison is also possible, shure, but will take much more time. And especially if I am offline, having no contact to the repository, then the files modification date is the only one indicator to see if and when it was changed (yesterday, last month, 5 years ago - this is an important information). So I know what I want: - on checkin, the files modification date must be saved - on checkout, it must be reassigned to the file. The only one problem is: because I have absolutely no deep knowledge of svn, I don't know how to do it. So I am looking for an easy howto .... Regards Henri
DougR
Most comparers (e.g. diff) do not use timestamps: they compare content. While the highly respected "rsync" program can use "time stamps" it is much better at doing backups, etc. when it uses checksums (the "-c" option). Given how much I know about timestamps I distrust them immensely. Before I go much further, what specific OS are you running your client on?
oHenri
Hello Doug thank you for the response. I understand your point of view - but mine is different, according to my previous explanations. And I understand your answer so that you can't and don't want help me. So I'm still looking for somewhere else who can help me to solve my request, as it is still: - on checkin, the files modification date shall be saved - on checkout, it must be reassigned to the file. As I read, this can be done by using a "custom property", but I have no experience to that.