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

RE: RE: Re: Getting the SVN command line to work with Tortoise and SmartSVN clients

From: Mike Craig <Mike.Craig_at_freeclear.com>
Date: 2006-05-12 17:32:31 CEST

YES! That was it, thanks for all your help.

-----Original Message-----
From: Mike Craig [mailto:Mike.Craig@freeclear.com]
Sent: Friday, May 12, 2006 8:26 AM
To: steveking; users@subversion.tigris.org
Subject: RE: Re: Getting the SVN command line to work with Tortoise and
SmartSVN clients

Aha! I think we are on to something. My SVN server is 1.3.0, but on my
workstation, my version is Subversion command-line client, version
1.2.1. I'll upgrade and try again.

Thanks.

-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of steveking
Sent: Thursday, May 11, 2006 11:14 PM
To: users@subversion.tigris.org
Subject: Re: Getting the SVN command line to work with Tortoise and
SmartSVN clients

Eric Hanchrow wrote:
>>>>>> "Mike" == Mike Craig <Mike.Craig@freeclear.com> writes:
> Mike> I am running in WinXP with the dot_net_hack environement
> Mike> variable set.
>
> I think that explains it. Each svn client distinguishes working copy
> directories from regular ones by the presence of a subdirectory named
> ".svn" ... except when you're using the dot_net_hack, in which case
> it's named _svn.
>
> Mike> I execute an svn co svn://ServerName/Project
>
> ... creating Project/.svn

With an 1.3.x Subversion client (not matter if GUI or CL), that should
be 'Project/_svn' if the dot_net_hack variable is set.

> Mike> I open Windows explorer, and using TortoiseSVN
>
> ... which looks for Project/_svn, and doesn't find it, which leads to
>
> Mike> it is acting like these are not subversion files at all.

The only thing I can think of right now which would lead to such a
situation:
* The env variable is set (no reboot after that)
* a checkout with the CL client creates _svn dirs
* TSVN is started from the shell, which was started *before* the env
variable was set: that means that process (and all that are started from

such a process) don't have that env variable set.
* TSVN still thinks it has to use .svn dirs because it doesn't know
about the env variable being set.

So: reboot (or at least restart the shell by killing all "explorer"
processes) after setting the env variable!

One other thing: the TSVN nightlies are built against Subversion 1.4.x,
which uses a new wc format. Once the wc is updated, it can't be used
anymore with older clients.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 12 17:35:51 2006

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.