Re: [Subclipse-users] "The file has been changed on the file system" when committing

Zach Bailey <zach.bailey@hannonhill.com> wrote on 07/06/2006 10:40:49 AM:

> For instance I committed something the other day (a single file by right

> click -> team -> commit). I got the commit email for it, and yet in my
> workspace I could right click on my project, select "properties", go to
> the subversion section and the "last changed revision" is still one
> revision prior to my commit - my project says it is rev 4327 while the
> HEAD revision is 4328. (it still says this in fact, almost a day after
> my commit).

If you right-clicked on the project or a folder then that is normal. When
you commit a file, the parent folders to that file are not advanced to the
same version. You have to run update for the folders to pick up newer
versions. Subversion refers to this as "mixed-revision" working copies.

This is actually quite easy to understand.

Assume you checkout your project when HEAD is at r10. Now another
developer adds a new file or two and the project is at r11 in the
repository. You now make some changes and do a commit so the repository
is at r12. The files you committed are at r12, but everything else is
still at r10. The folders could not be considered at r12 because the
files that were added in r11 have not been brought down to your working
copy.

There is a more thorough treatment of this topic in the SVN Book.

http://svnbook.red-bean.com/en/1.0/ch02s03.html#svn-ch-2-sect-3.4

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Jul 6 16:49:37 2006