Hi,
I don't think it is a bug anymore. I believe it is a feature :)
Altough in the mean time I upgraded to /version 1.2.0 (r14790)/, I am
able to reproduce the "problem".
Probably my problem was that the time of the server was actually in the
future. The commit time of a file is the time of the server and not of
the client (I assume this is a feature). So the commit was actually in
the future. And the time of file when checking it out is also in the future.
Michael
Ben Collins-Sussman wrote:
> Michael, will you please file this as a bug? It definitely sounds
> like a problem to me. (When you file the bug, point out that I asked
> you to file it.) Sorry for the delayed response.
>
>
> On Apr 29, 2005, at 7:20 AM, Michael.Brackx@alcatel.be wrote:
>
>> Hi,
>>
>> It seems the use-commit-times option does not take the time zone
>> into account. This gives problems as the checked out files can
>> appear to be modified in the future.
>>
>> scenario:
>> - server is in time zone -8
>> - clients are in time zone +1
>> - commit a file on a client
>> - check out the file on a client with the use-commit-times option
>> enabled: the file's last modified time is 9 hours into the future.
>>
>> server: subversion 1.1.4 (r13838), apache 2.0.54, windows 2000
>> client: subversion 1.1.4 (r13838), windows 2000
>>
>> Michael
>>
>> ---------------------------------------------------------------------
>> 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 Jul 19 19:11:04 2005