"MATHUS Baptiste" <mathus.b@mipih.fr> wrote on 11/13/2006 08:54:00 AM:
> +1 for the first behaviour : all the parent folders up to the root are
> marked as incoming changes when I commit a file in a folder. It's not a
> problem : I usually just run update, it does nothing and this
disappears.
> So, I don't really care about it, but in fact, it's a little bit
unuseful to
> have to do it, so if it is reproducible and correctable, I would be glad
to
> test it :-).
>
> I think I used to have the first part of the second problem too, but I
do
> not have it anymore. Isn't it because some repositories are contained
> "inside" some others ?
The second problem is an Eclipse bug that was fixed with 3.2.1.
The first issue is a very useful feature we added to Subclipse. If you do
not like it, you can turn it off by de-selecting the Show Out of Date
Folders option in the preferences. This is also on the Synch view's
drop-down menu.
When you commit files, all parent folders of that file are now out of date
in your working copy. Without this feature, the Synch view will never
show these folders to you as incoming changes, and thus if you only use
the Synch view, they never get updated. The problem then comes when you
do some operation that requires the folder to be up to date, such as
refactoring the folder name or setting properties on the folder.
With this feature in place, the Synch view works correctly and will show
when the folders need an update, as well as showing a Synch conflict if
you make a change that requires the folder to be up to date.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Nov 13 15:00:22 2006