RE: ".svn" directory name no good (in fact, it is worse than I thought)

++1
Yes I totally agree that this is an acceptable and viable solution. 99%
of Windows users won't ever want to give a *NIX user there working copy
and vice versa. The fact that this only affects the working copies means
windows clients can still use *NIX servers and vice versa. Also all the
third party utils are either platform specific or already have #defines
for win32 so this should be easy to do.

-----Original Message-----
From: B. W. Fitzpatrick [mailto:fitz@red-bean.com]
Sent: September 24, 2003 11:05 PM
To: David Waite
Cc: Files; james-tigris@jrv.org; dev@subversion.tigris.org;
sussman@collab.net; roncannes@hotmail.com
Subject: Re: ".svn" directory name no good (in fact, it is worse than I
thought)

David Waite <mass@akuma.org> writes:
> I'm not arguing for configuration, I'm arguing for the libraries, when
> compiled on for win32 platforms, use _svn for the directory name. I
> also am arguing against logic to 'support both' within the subversion
> libraries and command line client.

Excellent.

If you toss in some documention, and a FAQ entry on why we have _svn
dirs on windows, this has my +1.

-Fitz

--
Brian W. Fitzpatrick    <fitz@red-bean.com>
http://www.red-bean.com/fitz/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org