[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Custom Win32 binaries

From: Mladen Mihajlovic <mladen_at_hixnet.co.za>
Date: 2004-05-28 22:12:46 CEST

Whooooowwwiieee! After reading some of those threads I see why you guys
don't want to reopen this issue. Well I see that the issue has been
thoroughly thought through, discussed about and argued over. Thanks for
pointing me to those archives by the way, because I didn't know they
existed. I knew about the archives on Tigris, but I found the google search
was easier at www.contactor.se/~dast/svn.

-----Original Message-----
From: Jeff Cave [mailto:jeff.cave@sunergon.com]
Sent: 27 May 2004 11:37 PM
To: Mladen Mihajlovic
Cc: users@subversion.tigris.org
Subject: RE: RE: Custom Win32 binaries

On Unix/Linux systems directories and files with names starting with "."
are hidden.

The "." works just fine on Win, but Visual Studio does not like it at
all (as I understand it).

I don't have a problem working on both a linux and windows computer
working on the same code. Both use the "." notation.

-----Original Message-----
From: Mladen Mihajlovic [mailto:mladen@hixnet.co.za]
Sent: Thursday, May 27, 2004 2:17 PM
To: 'Branko Cibej'
Cc: users@subversion.tigris.org
Subject: RE: Custom Win32 binaries

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
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
make it .svn anyway?

-----Original Message-----
From: Branko Cibej
Sent: 27 May 2004 04:24 PM
To: Jostein Chr. Andersen
Cc: users@subversion.tigris.org
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
>>README.txt file:
>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
>trouble AFAIK.
Yes. That's their decision to make. Don't forget that TSVN is a
Windows-only project.

>It's a nice thing you are doing here and I think that the "_svn"
>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: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

  • application/x-pkcs7-signature attachment: smime.p7s
Received on Fri May 28 22:06:48 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.