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

David Waite wrote:
> 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.

Where is the "cost" in blowing away a working copy? A working copy is
extremely cheap - just check out a new one. I can't really imagine that
people are developing an emotional attachment to their working copies.

--
AnkhSVN: http://ankhsvn.tigris.org
Blog: http://ankhsvn.com/blog
IRC: irc://irc.freenode.net/ankhsvn
"We've got to find out what people want from fire, how they relate to it,
what sort of image it has for them.' The crowd were tense. They were
expecting something wonderful from Ford.`Stick it up your nose,' he
said.`Which is precisely the sort of thing we need to know,' insisted the
girl, `Do people want fire that can be fitted nasally?'"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org