ack, i got sidetracked. VS is just one of the problems fixed by
compressing the folder. even if you dismiss that advantage the others
are still there:
* 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 saves space, even without compression or even over a 'perfect' file
system
* it helps the tortoise SVN speed issues.
* it would be harder for people to accidentally hose the contents of
their .svn directory, and subsequently their repositories/working
copies. sometimes its best to keep the 'guts' of a product out of
non-expert hands, lest they hurt themselves. that's why you need special
tools to open the radium(?) casing in a fire detector. and thank
goodness, because i bet i'm not the only one who tried taking on apart
as a kid.
-alvin
Craig L. Ching wrote:
>>my point is that even superior products can die if not managed
>>correctly. if the SVN developers do not feel compelled to ensure that
>>SVN is compatible with VS, VS .NET, and any other tool that
>>may have a
>>problem with the .svn format because 'it is not our problem',
>>it is not
>>being managed correctly.
>>
>
> Dude, it's an open source project. If you feel so strongly about it, get the code and do something about it, that's the beauty of OS ;-) If there are so many VS.NET users affected by this (I use VS.NET on Windows as one of our many platforms, but I'm not affected by this problem), why doesn't some subset of that mass of developers pitch in and help out!
>
>
>>-alvin
>>
>
>
> Cheers,
> Craig
--
Alvin Thompson
Navy: 34
Army: 6
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 9 00:37:01 2004