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

Re: Handling of fat32

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-04-06 14:52:46 CEST

On 4/6/06, Michael Stather <stather.external@onespin-solutions.com> wrote:
> Yes, I did read your answer very well. Sorry I don´t understand why you
> write this as an answer, if you don´t want to help me nobody forces you
> to do so.

I just get upset when I answer questions but people choose to ignore it.

> Although I don´t understand what I did wrong.

1. You're asking about problems of the linux svn client on the TSVN list
2. I told you to "never access a repository or working copy on a
partition that's not fully supported by the OS". You know that it
doesn't work. But you still ask again on how to do it anyway.

> I do want to share my repository among windows and linux if it´s possible.
> And I know that the svn included in TortoiseSVN can use fat32
> partitions.

Every svn client on windows can.

> Even if svn fails when not being able to set the permissions.

svn won't fail setting permissions on FAT32 when used with a windows
client. That's why it works.
But it will fail with a linux client, because Linux (not SVN) can't
deal very well with FAT32.

> So my question just was "how do you do it"? Perhaps it´s better to use
> seperate working copies but if there´s a way to share it it would be
> much easier.

We don't do it. Because it doesn't work.
So you have to use two different working copies.

Stefan

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Apr 6 14:53:00 2006

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.