[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: retroactive mtime versioning

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-05-30 00:16:31 CEST

On May 29, 2007, at 16:51, Aryeh Leib Taurog wrote:

> Ryan Schmidt wrote:
>> On Mar 25, 2007, at 13:21, Aryeh Leib Taurog wrote:
>>> Then I heard from the client. They *must* have the original
>>> mtimes (for files I don't modify, obviously).
> >
>> If you want to store modification times of each file, I see two
>> options. One, you can commit each file as a separate revision,
>> then set the svn:date property of the just-committed revision to
>> match what the mtime of the file was. Repeat for all files.
>> Or two, you can attach a new property (e.g. x-mtime) to each time.
>> Set that property to the actual modification time of the file.
>> Perhaps invent a script which handles the commit, by attaching the
>> property and then calling svn ci. Invent another script to replace
>> svn checkout, which checks out, and then also sets the actual
>> mtimes of the files as per the contents of the new property.
> I've been playing with these two options for the last two months,
> but don't have what I consider to be a satisfactory solution.
> Either way I end up with something clumsy, slow, or both. I think
> the only viable way to do this would be to modify svn itself to
> maintain the mtime property. It's a pity it hasn't been done yet.

It has been done before: the text-time branch:


Unfortunately that code hasn't been touched in two years.

> For anyone who's curious, I've put the gory details of my struggle,
> along with all my scripts, at http://www.aryehleib.com/svn/svn.html

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 30 00:17:09 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.