I've chimed in with my two cents about this issue before;
I can't resist chiming in again.
VSS can maintain modification dates. I thought CVS did too; but, I may
be mistaken.
I'd also like Subversion to be able to save/restore modification dates
as a built-in property.
Our project depends on a third party open source project.
Normally I'd just use the binaries and not check them into source
control;
but, it happened that there was a missing feature. Someone else had
added that feature. I wanted to track the change of the feature
addition;
so, I put it all under source control.
Now, all of the file modification dates in the working directory
are different than the modification dates on the original files.
It would be nicer if they'd all stayed the same.
For a project you're starting from scratch - this isn't a big deal.
For a project that has a long unknown history and you're adding to it or
modifying it,
you'd like to maintain that history (in the form of modification dates).
I realize that the first person who adds such a project can do an
in-place import
(and then those modification dates would be maintained for that person).
I did that with VSS but the modification dates were lost with the
automated
conversion to Subversion.
Thanks,
Chuck
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Tuesday, February 22, 2005 11:37 AM
To: Scott Palmer
Cc: 'subversion' Users
Subject: Re: Feature request: Keep file dates
On Feb 22, 2005, at 10:22 AM, Scott Palmer wrote:
>
> The use-case that comes up here is for .pdf files or other content
> generated by non-programmers who do not directly use subversion. They
> hand a file over to the engineering team to incorporate into a build.
> On their own computers they have their own organization of the files
> and talk in terms of when they last updated the file, not when the
> engineering team decided to commit it to subversion. When I have to
> answer something along the lines of, "Did you get the changes I made
> last Thursday?" I can't go by the commit time that shows the
> following Monday because that isn't a strong enough indicator that I
> have Thursday's changes. Maybe I got an update on Wednesday and
> that's what I committed. If the timestamp (and size, etc.) matched
> exactly with the file that the creator has, I'm pretty confident that
> we are talking about the same thing.
Wow, that's really clear. Thanks for that explanation and example.
Maybe you should come persuade folks over on dev@ to increase the
priority and work out the implementation of this feature.
There's already an issue #1256 patch, but it needs a lot more attention
and discussion. (I'm tied up working on the locking feature right
now.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 22 18:52:33 2005