On Wed, 8 Mar 2006, Ryan Schmidt wrote:
> On Mar 8, 2006, at 06:05, Matthew Sanderson wrote:
>
> > I would like to be able to commit/import a file F1 to the
> > repository, then
> > check that file out or update it, yielding a file F2 in another
> > working
> > copy, and have F2's time of last modification be the same as F1.
> > Ie, the
> > checkin+checkout procedure should preserve the file's mtime. The
> > 'use-commit-times' config option doesn't do what I want.
>
> The use-commit-times option sets the modification time of files, on
> checkout or update, to the time they were committed. If that's not
> enough for you—if you need to store the actual modification time of
> the file, separately for each file within a single commit, then the
> meta-data-versioning branch may be for you:
>
> http://svn.collab.net/viewvc/svn/branches/meta-data-versioning/
> README.TXT?view=markup&rev=14236
>
>
Ryan,
Thanks! That branch looks to be exactly what I want.
It seems that in svn trunk, use-commit-times doesn't do what I want; but
on this branch and with the svn:text-time property set to enable this new
mtime save/restore functionality, use-commit-times does do what I want
(and doesn't do what it does in svn trunk).
I don't like this overloading of that config option. If the overloading is
to stay, then IMO the option should be renamed to 'use-repo-mtimes' or
maybe even 'use-repo-metadata' to reflect its new meaning. But I would
prefer two seperate config options. Still, regardless of its UI, this is
the functionality I was after.
Thanks again,
--matt
Matthew Sanderson
Senior Programmer (UNIX)
TCG Information Systems Pty Ltd
Sydney, Australia
matthew@formtrap.com
http://www.formtrap.com/
+61 (02) 8303 2407
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 10 01:58:36 2006