Eric Berry wrote:
> Mark,
> Please correct me if I'm wrong, I'm a basic user of the products, but
> doesn't Subversion version the folders as well. So if you commit your
> files from the synch view, then go to incoming changes, you technically
> should see the folders, because each of their revisions need to be
> updated. Whenever I commit my files, I always have to go to the incoming
> changes to update the revisions on the folders, and I don't see the
> files I just committed.
Right - that is the "show outdated folders" preference, which is turned
on by default in 1.2.3, but will be turned off by default in future
releases because it causes so much confusion.
You won't see the files you just committed in synch view, because the
commit updates the local revision number of that file when it commits,
so it's up-to-date with the repository and doesn't need updating. (I
didn't realize it did that, so that confused me in the first example
with my own files.) However, commit can't similarly update the local
revision number of the parent folders, since they might contain other
changes in the repository that you need to update.
> This might explain the issue where Jay isn't seeing his own committed
> files and only seeing the folders, but wouldn't help in the case where
> another colleague had made commits.
Right, that second case is really the only mystery.
> Jay, are you perchance doing updates outside of the synch view?
I may occasionally commit a single file direct from the RadRails
perspective, but all my updates are done from Synch view w/changesets on.
Jay
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Sep 7 18:19:42 2007