Simon Large wrote:
> On 05/12/2007, Stefan Küng <tortoisesvn@gmail.com> wrote:
>> tmto wrote:
>>> Hello,
>>>
>>> i run in the following error. I tried to rename a file in my working
>>> copy with TortoiseSVN but I got a error message "could not connect to
>>> server". That was right because the server was not availabe due a
>>> network error.
>>>
>>> But i thouhgt until today that subversion did not need a online
>>> connection to a server for local changes within the working copy.
>> Jein (sorry, had to use that German phrase) :)
>>
>> That means: it depends.
>> Now that merge tracking is implemented in the nightly builds, even
>> operations that were previously completely local sometimes need now to
>> contact the server.
>>
>> For renaming, that might go away until the final release. But for
>> example a 'revert' operation has to tell now the server that it also has
>> to revert the merge tracking info (e.g.: you do a reverse merge, but
>> then decide that it was a bad idea and revert the changes before you
>> commit - the server needs to know that the reverse merge was reverted).
>
> I thought the merge tracking info was held in properties, which don't
> get updated on the server until you commit.
Only *some* merge tracking info is stored in properties. The server also
stores merge tracking info (even more than on the client side),
currently using an SQLite db (but recent discussions on the Subversion
dev list indicate that the SQLite dependency might be dropped sometime
in the future).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Dec 5 17:26:15 2007