[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: Michael Stather <stather.external_at_onespin-solutions.com>
Date: 2006-04-06 17:48:04 CEST

Andy Levy wrote:

>On 4/6/06, Michael Stather <stather.external@onespin-solutions.com> wrote:
>
>
>>Stefan Küng wrote:
>>
>>
>>
>>>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
>>>
>>>
>>>
>>>
>>>
>>That was the answer I needed, thank you :)
>>Where should I know that a windows svn client baheves differently. I
>>assumed that they´re build from the same codebase.
>>
>>
>
>They are, for the most part, but in any cross-platform codebase there
>are bound to be blocks of code that are or aren't built for each
>platform.
>
>Maybe the Linux FAT32 FS module should allow users/applications to
>attempt to set permissions, and internally do nothing and return a
>success code every time? That way no application would get tricked by
>this. But that's a disucssion for LKML and I'm sure there are a
>million things that would be a problem which I haven't considered.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
>For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
>
IMHO a cross-platform app (and so also SVN) shouldn´t rely on setting
the permissions. It should perhaps print a warning
but shouldn´t abort. Or there should be a configure switch to disable
it. Other software like aMule does this, too

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Apr 6 17:48:22 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.