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

Re: What's the best and most common SVN Windows (Vista) Client

From: BRM <bm_witness_at_yahoo.com>
Date: Wed, 21 Jan 2009 13:06:19 -0800 (PST)

Yes, a simple hook script on the server side should do it.

But as stated, this is not an issue with the client per say - it's more that different pieces of software are compiled against different versions of the SVN library, and they are all client side. If someone uses and older client on a newer repository to work with it - even if they don't converse with the server using that client - then it will still cause the problem. People just need to make sure their tools are in sync with each other, and In know TSVN does releases when it changes library versions, sometimes that's the only difference to the previous release, though usually there are a few bug fixes in there as well.j

The SVN Devs were forward thinking enough to make future and past clients compatible, and be able to disable functionality appropriately. (e.g. future clients will disable functions not available on the server, and the server will speak with a client in its lingo instead of newer protocols if needed).


----- Original Message ----
From: Andy Levy <andy.levy_at_gmail.com>
To: John Gwinner <jgwinner_at_dazsi.com>
Cc: Robert P. J. Day <rpjday_at_crashcourse.ca>; Rez <pons32_at_hotmail.com>; users_at_subversion.tigris.org
Sent: Wednesday, January 21, 2009 3:07:53 PM
Subject: Re: What's the best and most common SVN Windows (Vista) Client

On Wed, Jan 21, 2009 at 14:27, John Gwinner <jgwinner_at_dazsi.com> wrote:
>> -----Original Message-----
>> From: Andy Levy
> ...
>> I routinely use the command-line, TSVN, and Eclipse on the same WC and
>> have had no trouble. The most important part is to make sure they're
>> all speaking the same language when it comes to the WC metadata - all
>> need to be based upon the same SVN version.
> Is there a way to lock out older clients from a repository?
> Most of our developers are at client sites, and it's hard enough to make
> sure their virus scanners are up to date, much less installed software.
> I could see when the next version is installed there being problems with
> people without outdated software versions. I can make it available on a
> private download, but people may put it off, especially if "it seems to
> work".

I believe someone posted a few months ago how to do it, but it's not
really needed except in special situations. Older clients will work
with newer servers (and vice versa), the newer features just won't


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-21 22:07:11 CET

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

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