Re: Subversion Problem - How to save file modify time?

Mark Phippard wrote:
>>
>> I'm fine for reopening the debate; we should first examine why
>> exactly we've kept this branch in stasis for so long. If we don't
>> like the design, what would a better design be?
>
> Having used other version control systems that have this feature, I
> always thought Subversion should have it too.

Did those systems do anything sensible when then committing system
clocks were in the wrong century or if files were dated in the future?
One advantage of using commit times is that they can be forced to be
consistent.

> My problem with this
> has always been the design. I do not think you can do this feature
> properly on top of Subversion's repository today.

> Using a versioned property sucks. That means you have to carry around
> the property information in the working copy and every commit in
> theory needs to update it. This fouls log and diff etc..

It would be nice to have the value stored whether you use it or not,
though, with tools to view it and restore it even if you don't restore
by default.

> In theory revision properties could be used, but do we really want an
> import of 10,000 files sticking all of that data into revision
> properties?

Or worse, if you accidentally do something that touches the timestamps
on your working directory (perhaps copying to a new location) and
commit, should that be a new revision for every file?

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org