Mark Phippard wrote:
> The issue is that updating to HEAD is the easiest thing to do, but it does
> have a potentially negative side effect that if commits have been done to
> your project since you opened the Synch view, then updating to HEAD is
> going to include those commits even though they did not appear in the Synch
> view.
I guess I don't understand. Here is what I expect to happen:
When I do a synchronize view, I get a list of incoming changes. I expect
these to reflect HEAD. Now between the time that I have done the
synchronize and when I do anything with it there may be any number of
commits. The notion of Synchronize View is much like doing a "Check for
Modifications" in TortoiseSVN. It is only meaningful at the moment it
was run and after that its meaningfulness decreases.
The files in my synchronize view are still out of date with respect to
my working copy. When open any one of them, I expect to see the
difference between what my working copy has and what HEAD currently is.
And when I update these, I expect to get HEAD. I also expect that I get
nothing else. Now, I know that if there have been intermediate commits,
the files I am getting may be broken.
Because my expectation does not meet reality, I specifically select the
files I want to update and update only those.
In practice, I find it is better to use Synchronize merely as a "Check
for Modifications" unless I am the only one working against an isolated
section of the repository and use Update from the Team menu to get all
changes.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Feb 26 15:34:05 2006