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

Re: TortoiseSVN 1.6.2 vs. Subversion 1.5.4

From: ThanksButNo <no.no.thanks_at_gmail.com>
Date: Sun, 17 May 2009 00:20:48 -0700 (PDT)

On May 16, 11:59 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
> ThanksButNo wrote:
> > Hello --
> > I have downloaded TortoiseSVN 1.6.2 from the website.
> > And, I have downloaded Subversion 1.5.4 fromwww.sunfreeware.com,
> > because that is the latest compiled binary package for Solaris 10
> > sparc that's available there.
> > Might there be any known "gotchas" in pairing these two versions
> > together that maybe I ought to be aware of?
> As long as you don't share the working copy or access the
> repository via file:/// urls you're fine.
> Stefan

Thank you, Stefan! No worries on file URL's. The whole
idea was to set up access via the web over Apache, since
our workforce is globally distributed. The only one with
direct file access on the Unix server is me, and I'll be
using TortoiseSVN from my PC!

That puts in mind another question: I need to access the
server from the LAN. I'm behind the router. So I use a
URL like: From outside the
LAN at a remote site, they need to use the domain to get
to the router and the router redirects to the SVN server,
e.g., http://svn.ourdomain.com:8051/etc.

I know the router and everything works from the network
and subversion side, because people have been able to
connect in, login with password, and browse to the source
code that I had committed earlier. (And tell me what was
wrong with it!)

So the question is: is there a possibility that Tortoise
will get confused if different people commit changes to
the same Real Location using different URLs?

-- gratitudes and appreciations --


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-17 09:32:01 CEST

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

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