i forgot to mention perhaps the biggest reason of all: it helps control
access to the .svn folder contents. how many pleas for help have the
subversion guys fielded because some dweeb accidentally modified the
contents of that directory and subsequently hosed their working
copy/repository? the plea for help usually starts with something like,
'i did some sort of automated find/replace and forgot to exclude the
.svn directory...'
-alvin
Alvin Thompson wrote:
> um, i'm not following you. how is it high-cost in development resources?
> there are only about a billion libraries out there that facilitate
> compressed folders, and even a 6-year-old or older processor can keep
> up. it probably wouldn't significantly change more than a few lines of
> code.
>
> as i see it, it solves these issues:
> * it saves space, even over a 'perfect' file system
> * it prevents false hits using most 'file find' tools
> * it prevents whining from fools who don't know how to configure their
> build scripts to ignore SVN directories
> * it helps alleviate the problems .NET weenies have been having
> * it helps the tortoise SVN speed issues.
>
> basically, it fixes all apps (including those not mentioned above) which
> have to recursively scan folders to do their job. you don't think this
> is a more elegant solution than requiring every other program on the
> planet to be 'SVN aware'?
>
> -alvin
>
>
> Andreas Kostyrka wrote:
>
>> On Mon, Mar 08, 2004 at 12:19:40PM -0500, Alvin Thompson wrote:
>>
>>> +1. it's a low-cost solution that would help solve many issues.
>>
>>
>> Actually it's high-cost (in development resources) solution to a
>> non-issue?
>> (a bug in some MS tools?)
>>
>> Andreas
>
>
--
Alvin Thompson
Navy: 34
Army: 6
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 8 19:16:26 2004