As I understand it, Windows keeps three "dates" per file:
Created Date, Modified Date, Accessed Date. I am a little confused by your
explanation since none of those dates should be equal to their counterpart
dates in the textbase version (I checked to make sure that this is the case).
Also, I went back to make sure that the WC version of the file file was
substantively different than the textbase version just to make sure I wasn't
doing anything dumb.
landon
Ben Collins-Sussman wrote:
>subversion@lclark.net writes:
>
>>Hi,
>>I have been using SVN internally for a few months. Here is a recipe for
>>reproducing this error:
>>
>>1. I already have a WC in WC1 with a file called browse.html with a modified
>>date of 11/8/2002.
>>2. Check out a fresh working copy in another directory: WC2. This gives
>>all the files a modified date of 11/12/2002.
>>3. Copy browse.html from WC1 to WC2. The modified date stays the
>>same (11/8/2002).
>
>
>Well, heck, that's the bogosity right there. Is that normal on win32?
>When you copy a file, the timestamp doesn't change?? I've never heard
>of such a thing.
>
>>4. svn st and svn st -u both return no changes to WC2.
>>
>
>Right. The first check we make is whether the timestamp has changed.
>If the timestamp hasn't changed, svn assumes it couldn't *possibly* be
>modified. (If the timestamp has changed, then svn resorts to
>file-size and possibly brute-force.) This is exactly what CVS does as
>well.
>
>So what's going on here is an odd copy behavior on win32, which
>doesn't match unix behavior. What's the right solution?
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 12 21:15:19 2002