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

Re: .svn vs _svn on VS.NET (ASP.NET)

From: David Waite <mass_at_akuma.org>
Date: 2004-03-09 02:00:52 CET

I agree - the last time this came up, I would have been very much in
favor of having #define's for different wc dir names for platforms -
now, we have many users of both which would need migration. The cost of
either revamping the existing working copy code or making people who
have downloaded the 'stable' 1.0 version having to blow away all their
working copies makes the cost too high now.

And FWWIW, I am saying this as a blue-moon subversion contributer as
well as a developer who has a ASP.NET project under VS.NET 2003

-David Waite

On Mar 8, 2004, at 5:14 PM, C.A.T.Magic wrote:

>
> ----- Original Message -----
> From: "Garrett Rooney" <rooneg@electricjellyfish.net>
> [...]
>> If we MUST make a change to account for this, I would prefer that it
>> be
>> to allow either .svn or _svn, perhaps with a preference to toggle
>> between them (default to _svn on windows, .svn on unix), and we
>> explicitly disallow both in the repository.
>
> plz leave the -default- as it is now ( .svn ) or you will break
> existing repositories and scripts.
> remember: this is a workaround for a very few IIS/VC users.
>
> :-)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>

  • application/pkcs7-signature attachment: smime.p7s
Received on Tue Mar 9 02:01:23 2004

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

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