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

Re: TortoiseSVN 1.5.0-alpha1 - compatibility

From: Ulf Zibis <Ulf.Zibis_at_CoSoCo.de>
Date: Mon, 24 Mar 2008 19:10:07 +0100

Am 24.03.2008 08:48, Stefan Küng schrieb:
> Yes of course. I thought that was clear, sorry. A Subversion client
> only updates the working copy format if you actually *use* it on a
> working copy where the working copy would get changed anyway (but
> those are most commands).

Thanks for this answer, so it's clear, that we don't talk at cross-purposes.

> Yes, TSVN doesn't use svn.exe at all.
> But you could install the Subversion binaries version 1.5.0-beta1 and
> then have your netbeans IDE use those instead:
> http://merge-tracking.open.collab.net/
Very much thanks for this interesting link. Unfortunately it's only
talking about eclipse client plug-in.
 From where get the sureness, that I can use the Subversion binaries
version 1.5.0-beta1 with the NetBeans IDE?
There is no information about that:

>> Conclusion:
>> Please show a BIG warning dialogue BEFORE TortoiseSVN starts
>> upgrading parts of the WC to a new version, with the hint, that only
>> 'reading' commands are harmless, and give a choice to abort.
> Such a warning is not really possible. Because TSVN doesn't know
> beforehand if a command would update the format or not - it depends on
> the command parameters and the server/repository.

So IMO subversion libraries should report/return this warning. Don't them?
However, TSVN could give a warning about *possible* working copy
incompatibility problems on every command, which *possibly* upgrades the
WC after verifying the format of the current WC.
In worst case on all commands.
This would avoid users from the mess I had.


To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-03-24 19:10:23 CET

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

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