On Wed, Sep 16, 2009 at 12:40 PM, Andrew J G <andrew.gray_at_rcrt.co.uk> wrote:
> I think that I understand most of what was in those links. I will post when
> I see things that dont seem to fit.
> One of the things that I have noticed a number of times is what seems to me
> to be odd behaviour when I delete directories from within the IDE.
> For example - I have a project - in that project there was a directory which
> contains some redundant source code. I deleted the source code files from
> within the IDE - then committed the entire project - that works fine. Then I
> delete the (empty) directory - again within the IDE - the appropriate
> 'cross' symbol appears next to the directory entry.
> However, now if I try to commit the entire project - this commit fails -
> telling me that the corresponding directory in the repo is 'out of date'.
> Here the whole project was commited immediately before the directory was
> deleted - so the repo version should definately be 'up-to-date'.
It is not the repo that is out of date, it is the local working copy.
This is the exact sort of scenario the posts I pointed you to
describe. When you do ANY commit in your working copy, after the
commit completes your working copy is ALWAYS out of date. The blog
post and links on mixed-revision working copies explains why.
The issue is just that most day to day operations do not require your
entire working copy to be complete up to date so you do not notice it.
A few operations like deleting a folder or setting folder properties
make it come up.
Of course people have files out of date all the time, but that
situation is so normal and obvious it does not cause the confusion
that folders do.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-09-16 18:49:19 CEST