> That's no proof! Those are the data from the files on your harddrive.
> But you can't tell which version is loaded in memory. If only *one*
> single app has for example the dll still loaded, then *that* version
> is used, even though there's a newer one on the harddrive.
Sorry Stefan, no meant to get you angry however I tend to disagree with you.
About "TortoiseSVN.dll" - you can try replacing/modifying/deleting/whatever with it when the explorer is using it. You'll fail. Then, the only way it can be updated is when it is not used => when it is loaded again it is loaded from the disk => the new version is used.
About "TSVNCache.exe" - I personally killed it and watched it missing for more than 15 seconds then it was loaded - again, from the disk.
Although restart is a nice thing, I can't allow it to happen more than once a month so I'll continue this way and since I fail to comply with the requirements for a restart I'll stfu.
>> nono... a folder which is used in many projects via externals, i.e.:
>>
>>
>> Project/trunk
>>
>> --SHARED
>>
>> --App1
>>
>> --App2
>>
>> --App3
>>
>>
>> The "SHARED" is being svn:externals from the three apps, so when checked out
>> it looks like:
>>
>> --SHARED
>>
>> --App1
>>
>> ----SHARED
>>
>> --App2
>>
>> ----SHARED
>>
>> --App3
>>
>> ----SHARED
>>
>> If I modify the contents of the SHARED from inside App1 for example and
>> checkout, none of the others gets any notification of what happened. This
> That has nothing to do with the cache!!!!
> If you modifiy something in App1->SHARED, then those modifications are
> available to the others (app2, app3) only after you commit
I did. The repository is updated with the newest version of "SHARED", but neither "SHARED", nor App2->SHARED or App3->SHARED were marked as changed. If I manually "Update" them, they got the newest version.
App1->>SHARED and update App2 and App3.
> Please read the docs. And I strongly recommend you also read the
> Subversion book, especially the part about externals. You seem to have
> completely misunderstood how those work.
RTFM as always...
I did but will do again, maybe missed something.
>> Just tried:
>>
>> Project/trunk
>>
>> --Dir1
>>
>> --Dir2
>>
>> --Dir3
>>
>>
>> Moved Dir1 to subfolder of dir3
>>
>> Project/trunk
>>
>> --Dir2
>>
>> --Dir3
>>
>> ----Dir1
>>
>> Done a cleanup, it passed ok, then tried to commit - "Entry for
>> Project/trunk/Dir1 has no valid URL"
> Did you move it in explorer, or did you use the right-drag context
> menu TSVN offers you? If the first, the error message is expected.
This one I obviously missed. Will use the right drag in the future.
Received on Mon Aug 29 13:39:25 2005