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

RE: [Subclipse-users] svnkit requests [was Re: [Subclipse-users] Subclipse release coming soon]

From: MATHUS Baptiste <mathus.b_at_mipih.fr>
Date: 2006-12-07 09:04:48 CET

De : Dan North [mailto:dan@tastapod.com]
Envoyé : mercredi 6 décembre 2006 22:49
À : users@subclipse.tigris.org
Objet : [Subclipse-users] svnkit requests [was Re: [Subclipse-users] Subclipse release coming soon]
> 1. Can you make the default behaviour in svnkit to not upgrade a working copy? It's extremely frustrating to have a subversion client change a WC so that other clients on the same machine can no longer use it.

Well, I think that wouldn't be a good solution, because the JavaHL implementation (isn't it the reference, right ?) does this by default. So, if you want a svn client not to upgrade automatically the wc, I guess you should begin by trying to convince the svn team to do this. Then, it would completely make sense to also do this in SvnKit.

At the moment, IMO, it would be far worse if SvnKit would behave differently than JavaHL by default :-/.

> 2. If svnkit moves (delete+add) a file into a new directory, the metadata is updated from 1.3 to 1.4 anyway, regardless of the upgradeWC setting. Again this means I can no longer use my command line client.

OK, here I agree this seems to be a problem though :-).


-- Baptiste

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Dec 7 09:05:43 2006

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.