On Tuesday, July 9, 2019 at 7:37:16 PM UTC+2, Joe Chlimoun wrote: > > Hi, > > I'm trying to preserve the original modification date for files being > added into SVN, rather than the add/check-in date or the check-out date. >
you know that "modification date" is not the same as "commit date"? > > Currently I'm doing this through a very slow and painful method: Iterate > through files, commit one at a time, revprop change after the commit to set > the revision date to the file's modified date. This produces THOUSANDS of > tiny revisions, which makes working with the repo harder (ie, can't check > out a random revision as it might be broken/incomplete, admin operations > are much slower than they should be, etc). Is there a better way to do this > using custom properties and either server side or client side scripts? > > I'm not just a masochist... my application is extremely sensitive to file > dates. > What you're doing is basically rewriting history. And that's bad. You're changing the commit date (that's what that date in svn is, not a file modification date). Which means you can (and will) get situations where a commit has files with commit dates that are after commit dates from a future commit. Meaning the revision numbers increasing won't mean that file dates also are increasing. -> that can work for a while, but will definitely break some svn commands because that's now allowed to happen. -- 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/9e4376d7-c5e4-4d94-99d5-02c236185079%40googlegroups.com.
