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

Reducing "out-of-date" errors

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-07-31 15:31:48 CEST

Over on the Subclipse list (I also see this on users@ and TortoiseSVN
lists) we have been getting a lot of activity from new users that are
really confused by the out of date errors they get. I think we see this a
lot more in Subclipse because the Eclipse IDE encourages refactoring which
leads to a lot of moves and renames.

The biggest problem we run into is with new users working alone with a
repository. It is easy to understand how someone with one project and one
working copy working by themselves can get confused by an error saying
their project is out of date.

This might be a crazy idea that goes against all of the design principles
in the code, but would it be possible to enhance the commit process so
that after committing revision N, any "parent folders" to the committed
files that are at revision N - 1 be advanced to revision N? This would
keep the folders at the HEAD revision unless another user makes commits to
the repository. It seems safe on paper, but I do not know what the code
implications would be.

Just a thought, I'd appreciate any comments. I spend a lot of time
explaining and defending this problem to users.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 31 15:32:23 2006

This is an archived mail posted to the Subversion Dev mailing list.

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