John Peacock wrote:
> In the sense that the bug is in IIS, you are correct. That being
> said, I have no illusions that M$loth will fix their buggy software
> anytime soon.
>
> There have already been suggested patches to use _svn for Windows;
> feel free to apply those to your private copy. Someone may decide to
> provide prebuilt binaries for Win32 users without the capability of
> building your own. However, I have to vote with the other developers
> who say this is not Subversion's problem to fix.
[de-lurk] FWIW, I'm someone who's only just started using Subversion,
but love it to bits already (it reminds me a lot of Perforce). I'm not
doing .Net development at the moment, but am likely to in the near
future, and would like to be able to advocate using Subversion on my
projects. I wouldn't be able to do this if Visual Studio.Net can't work
with it (regardless of the *reason* it doesn't work or whose fault it
is). The only way forward would be for me to use a private, patched copy
of Subversion that used the _svn workaround -- not something that would
improve the chances of us adopting Subversion.
Just wanted to add a voice to those asking for a workaround. Of the
suggested workarounds, anything that changes structure in-place from one
format to another is bad news -- a default of _svn with graceful
fallback to .svn on broken platforms (i.e. Windows) sounds the best bet.
Cheers,
Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 29 11:46:10 2003