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

Re: Keeping last-modified dates

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-30 15:32:42 CEST

On Aug 30, 2006, at 14:43, Gale, David wrote:

>> The problem with that is obviously the initial import: If I'm
>> importing a project that's been developed without version control
>> over the past two years, I don't suddenly want all of the files in
>> the project to have today's (or any other) modification date. I want
>> each file to remember the date on which that file was modified. As
>> has been explained by others, this is useful information.
> Importing files doesn't change the modification time. Do an in-place
> import, and you'll have a working copy with all of your precious old
> modification dates intact; the mod dates will only be touched when you
> actually modify the file (or update a file that someone else has
> modified).

Well, yes, but that applies only to that one local working copy. As
soon as I check out a new working copy, or if someone else checks out
a working copy, they don't see the original dates. They see either
the current date or the import date, depending on whether they're
using use-commit-times or not. I want the original modification dates
preserved in the repository where they belong. Through use-commit-
times or a similar option, users would still be free to select
whether they want their working copies created with this additional
metadata or not.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 15:50:44 2006

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.