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

Re: Timestamp Issues

From: Tom Rawson <trawson_at_clayst.com>
Date: 2004-11-30 02:40:46 CET

On 29 Nov 2004 Kris Deugau wrote:

> When you svn up, if someone has committed changes to a file, that file
> should have a newer timestamp either way - and if the changes from
> someone else's change conflict with changes you've made since your
> commit, the timestamp on your file will be newer still once you've
> resolved that.

I think you're right if you're talking about two people working on the
same file. I think Patrick was talking about this case:

        I check out a file at 9:00
        At 9:15 someone else modifies it
        At 9:20 they commit the mod
        At 9:30 I do a build
        At 9:45 I do an svn up
        I do another build

At this point if the modified file has a 9:45 timestamp (time of the
update) my make will notice it. If it is 9:15 (time of modification)
or 9:20 (time of commit) my make will not notice it. In this scenario
you want to know when the changed version "arrived" on the local
machine, not when it was changed.

--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 30 02:46:54 2004

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.