Re: [Subclipse-users] [Subclipse-users] subclipse commit requires update

On Tue, Sep 15, 2009 at 4:38 PM, Andrew J G <andrew.gray_at_rcrt.co.uk> wrote:
> I am new to svn/subclipse.

See this explanation:

http://markphip.blogspot.com/2006/12/mixed-revision-working-copies.html

> As I understand it - in normal use - 'update' brings my working version 'up
> to date' with the repo, and 'commit' posts my working version to the head of
> the repo.
>
> I have a dedicated svn repo for several development projects - to provide
> version control - this one is not currently shared with anybody else.
>
> What I see - almost every time that I try to commit a project is that the
> commit initially fails - complaining that files are 'out of date' - and
> advising me to do an update first - before trying to commit.

You are probably getting the errors on folders. There are a handful
of operations that require the folder to be at HEAD, such as modifying
the properties of the folder. So even though you are the only one
working your working copy can get out of date.

This is all core Subversion stuff, it is not caused by Subclipse.

We used to have a feature to help make this more clear, but people
were so annoyed by it we turned it off by default. See:

http://markphip.blogspot.com/2006/12/subclipse-synchronize-feature-show-out.html

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2395249
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].