Mark Phippard wrote:
>
> In Subclipse we have this "Synchronize" view that lets you graphically
> Synch your WC with the repository. This might include graphically merging
> changes manually etc... Anyway, for correctness, we have used update -r N
> to perform updates so that if additional commits have been made since the
> process started the user does not receive any unexpected updates.
I don't know Eclipse or Subclipse. Please could you explain in more detail the
sequence of Subversion operations that is involved. When you say "We have used
-r N" do you mean Subclipse chooses a particular revision number (which one?)
to update to and then performs multiple updates (why? where?) to that same
revision?
> The problem is that if a user does a commit before they do updates, then
> when they come back and do an update at their root folder, the update
> process removes what they just commited from their WC. We cannot just
> update the revision based on the commit because to do that you would really
> have to just rerun the whole process, which from a performance point of
> view is not desirable.
>
> Just venting I guess.
I don't yet understand the problem. Are all of these user operations (commits,
updates) done from within Subclipse? What's the significance of your words
"come back and do an update at their root" and "rerun the whole process"?
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 28 02:24:09 2006