Re: Is there really no way to keep the file modification time intact?

Frans Knibbe wrote:

[...]

> If I read your script correctly, you commit a file and then you use svn
> propset to alter the svn:date property. Well, that is a nicer way of
> doing it, indeed. I did not realize this was possible. But now I have
> also read the warning in the SVN book:
>
> "Since the timestamp of a revision is stored as an unversioned,
> modifiable property of the revision (see the section called
> "Properties", revision timestamps can be changed to represent complete
> falsifications of true chronology, or even removed altogether. This will
> wreak havoc on the internal date-to-revision conversion that Subversion
> performs."

I don't know about "internal date-to-revision conversion that
Subversion performs".

Since my script sorts the files before committing, I don't think that
there can be any problem.

> Have you ever noticed any havoc resulting from you migration? If I

No. But I used it only for initial import of a small number of soucre
file trees.

> understand correctly, the effect to avoid is the -r{DATE}switch
> returning a wrong revision number. So if I first sort all the objects I
> want to commit by date, there won't be a problem. I hope...

That's what my script does and why I wrote it.

Oliver

-- 
Oliver Betz, Muenchen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org