Sorry, somehow this response did not go to the list.
attached mail follows:
My teams and I often take work home for the weekend
then go through the hassle of attempting to check
them back in on Monday -- it would be cool
if svn could handle this use case more easily,
and recover from the unnecessary conflicts
more easily.
Les Mikesell wrote:
> Jeff Smith wrote:
>
>>> Or, you might copy some files out to work on a different machine where
>>> the clock setting is wrong, than copy back with a method that
>>> preserves that wrong timestamp.
>>
>> Not even the same thing--Subversion does not need to compare
>> timestamps with the repository, only with the local "pristine copy".
>> This talk of moving the working copy to another system is risky, and
>> outside the scope of subversion.
>
> But it almost certainly happens. Perhaps not the whole working copy but
> consider the scenario where someone wants to edit a few files
> elsewhere, zips them up, does some work on another machine, zips the new
> versions up the machine with a different clock, brings them back and
> unzips on top of the original. I'd expect that to happen all the time.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 15 15:35:35 2007