On Jul 17, 2008, at 02:56, Benjamin Smith-Mannschott wrote:
> My worry with 'preserving mtime' in the repository, is that it's not
> clearly defined what this should mean.
>
> We have an n to 1 mapping problem: We have one date to work with on
> the local file system: mtime, but at least three meanings we might
> want to give it:
>
> (1) The time, local to the working copy, when this file was last
> updated there. (the current default).
>
> (2) The time, local to the server, when the file was last committed.
>
> (3) The time, local to the working copy, that the file claimed to have
> as its mtime the last time it was comitted.
>
> Currently, we have (1) and (2) available. For my purposes, (2) seems
> the most natural, though (1) is the default.
>
> What people seem to be asking for is (3), but what exactly do they
> mean when they ask for this?
All I care about is preserving existing historical information on
import or add. I have songs I wrote four years ago, php projects I
developed three years ago, photos I took last year, and I want to
import them into a Subversion repository now, and I do not want to
lose the modification date and time currently on those files. After
they're in the repository, I'm perfectly happy with what Subversion
already provides, preserving the commit time and not the modification
time.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-17 10:40:47 CEST