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

Re: [TSVN] Problem with TSVN 1.1.0 and working copy in the root of a network drive

From: SteveKing <steveking_at_gmx.ch>
Date: 2004-10-08 18:35:41 CEST

Andreas Mayer wrote:

> for several weeks now, I have used Subversion and TSVN 1.0.8 to version
> my home directory on a Windows XP machine. The home directory is on a
> Windows file server and mounted as a network drive (let's say as H:). So
> far, this setup worked flawlessly and I was very happy with it.
> Today, I switched to TSVN 1.1.0 and everything works fine as long as the
> working copy is at least one level under the root of the respective
> drive, for example H:\test. I can checkout directly to H:\, but whenever
> I try to commit changes in H:\ or to view the log of a file in H:\, a
> new process named TortoiseProc is started and takes up CPU time, but no
> dialog pops up. Until now, I have terminated these processes manually
> after some minutes.
> I oberserved, that when I delete H:\.svn after a new TortoiseProc was
> revved up, the dialog will finally pop up -- but shortly thereafter,
> TortoiseSVN will crash and prompt for a bug report.
> By the way, my repository is on a Linux machine and accessed via
> svn+ssh, but the same behaviour is shown with a local repository on C:
> or one with FSFS on H:\somewhere.
> Is it possible to have a working copy in the root of a network drive
> with TSVN 1.1.0 or is this a defect?

Fixed in revision 1793.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 8 19:42:36 2004

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.