Mark Phippard wrote:
>
>>>User selects some files, or perhaps a common parent folder and chooses
>>>update. We run:
>>>
>>>svn up -r N
>>>
>>>Where N = highest revision number of selected items
>>
[...]
> The previous answer probably clarifies, but N is chosen based on the
> highest last changed revision of the items you selected.
But that seems to conflict with what you wrote in the previous message:
>>> If a user does a commit after populating the view we have not done anything
>>> to refresh the view, because svn st -u is fairly expensive. The problem is
>>> that if they select say the root folder and run update, then the value of N
>>> is always less than the value they just committed.
Here you seemed to be saying that when a user runs "update" this second time,
it uses a different definition of N, one that is not the highest last-changed
revision of the selected items.
Ah, I see, the value of N is the same in both updates because the definition of
it is only the highest such number that was cached locally in the earlier step
(when "Synchronize" was chosen and a "status -u" was performed), and this cache
hasn't been updated to account for the commits that were performed in the mean
time. You're back to the problem of specifying exactly what you want conceptually.
Sorry if this is not much help.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 1 02:20:42 2006