For the life of me I can't figure out why did is such an "UN-official"
feature. I got the feeling that subversion was very well designed so it
shoudn't be a problem to change should it? So if it's just a matter of
changing the directory, then why would that introduce bugs (aside from the
fact that people running normal subversion would not see a working copy)? Is
it something to do with different operating systems? What was the reason to
make it .svn anyway?
From: Branko Cibej [mailto:firstname.lastname@example.org]
Sent: 27 May 2004 04:24 PM
To: Jostein Chr. Andersen
Subject: Re: Custom Win32 binaries
Jostein Chr. Andersen wrote:
>On Thursday 27 May 2004 15.51, Branko Cibej wrote:
>>I have decided to make available an unofficial build of the latest SVN
>>binaries for Windows that use _svn instead of .svn for the
>>administrative directory. Look in http://www.xbc.nu/svn/.
>>The Subversion project has nothing to do with these binaries, I have
>>not tested them in any way, do not promise that they will work, will
>>not provide an installer, etc. etc. Here's an excerpt from the
>How about making them at the same time as the ordinary binaries and
>include them in the standard Windows installer (and also upload them on
>the Subversion site after all).
IIRC we've already decided that we won't do that, and I don't want to
reopen that discussion.
>TSVN have offered a _svn solution for a while without too much noise and
Yes. That's their decision to make. Don't forget that TSVN is a
>It's a nice thing you are doing here and I think that the "_svn" binaries
>should be as avable as possible without making your server bleed IMHO.
Oh, I don't expect 10k downloads a day, or even 10k downloads overall.
So I won't bother with a better solution until bandwidh does become a
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 27 22:11:30 2004
- application/x-pkcs7-signature attachment: smime.p7s