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

Re: [RFC] MTime functional specifications (v2.0)

From: Philipp Marek <philipp.marek_at_emerion.com>
Date: Fri, 5 Feb 2010 08:24:27 +0100

Hello Ed,

some more comments.

On Freitag, 5. Februar 2010, Ed wrote:
>+Issue #1256 was entered into the Subversion issue tracker on 24th April
> +2003 and has been opened since then. A few patches have been submitted;
There's even a branch with a full implementation in the subversion
repository, and it's been ported to relatively current versions - maybe
that's what you mean by "patches" here.

>+ - Whenever Subversion modifies a file (or directory) in the WC, and
>+ there are local changes to that node, such as when updating a file
>+ that the user has been editing, it shall update the mtime property.
This isn't implemented in the branch, AFAIR.

>+ Mtime shall be stored in a versioned property named 'svn:mtime'.
>+ Any file or directory may have this property. The format of the
>+ property value is 'YYYY-MM-DDTHH:MM:SS.UUUUUU' of which the time
>+ is UTC.
Very fine. And if you change that to "svn:text-time", this is already
specified in svn_props.h:

>+ ... This functional specification takes
>+ the tact of setting the 'svn:mtime' property to the current
>+ mtime as it will give the user at least a starting point
>+ to which to make their statistical/informational mtime references.
So there's no way to have some part of the WC with mtime-storage, and another
without? I'm thinking about generated binaries that you want to keep.

Maybe the property should just be set (on commit) if it already exists.
(That's what the branch does.)

Thank you for working on that!


Received on 2010-02-05 08:25:01 CET

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