[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] SVN: Accepting new directory versions "hides" my locally updated files (outgoing updates)

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 22 Apr 2008 09:40:45 -0400

On Tue, Apr 22, 2008 at 9:36 AM, John Chesher <jchesher_at_hobsons-us.com> wrote:

> I'm an old CVS user that recently began using SVN. I've read many threads
> in the archive beginning like that ;-) and I suspect that I just don't
> understand how Subversion is intended to work, so I'm hoping someone can
> shed light on this scenario.
> Say for example I begin with an Eclipse project that is synched with SVN, I
> edit 2 files, then do a synch and commit ONLY ONE of the files. My Team
> Synch perspective now shows me that I have incoming updates for all
> directories in the past that lead to the file I changed. So, I accept those
> changes into my workspace. At this point, the second file (the one I
> updated but did not commit) disappears from my Team Synch perspective. I
> can re-synch the project and it still doesn't appear. The only way to get
> it to show up there again as a file with an outgoing update is to do a
> Team-Synch on just that individual file. Then, I can do a synch on the
> entire project and it will show this file as containing an outgoing change.
> Can anyone explain this behavior and whether I am doing something wrong,
> have a wrong assumption of how it should work, or if this is an SVN bug?

There have been some bugs fixed in this area. What I would recommend,
until you can move to the new 1.4.0 release when it comes out, is that
you go to your preferences and under Team > SVN, deselect the option
to "Show Out of Date Folders".

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-04-22 15:40:57 CEST

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.