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

On Wed, Sep 24, 2003 at 08:57:00PM +0000, Ronald Cannes wrote:
> >svn export
>
> How is that going to help me?

Sorry I misunderstood and thought you were looking for a way to remove
the .svn directories from the published release, not the development
copies. It can still be done but would take more space as you would
need to have a working copy and two exports. One export would be the
pristine copy and the other would be your editing copy then you'd diff
the two and apply the diff to the working copy.

> >Windows can handle it, the individual applications are the problem.
>
> Applications that *ship* with Windows cannot handle it! Try creating a
> ".svn" directory using the File Explorer. It won't work.

However "mkdir .svn" from a command prompt (cmd under WinXP) does.
This is simply another case of Windows not supporting it's own
functionality (aka broken software).

> Also, some of the Win32 SDK functions cannot handle it, at least not
> the .NET version of those functions.

Those would be broken functions.

> I see no reason why this shouldn't be changed this into something that
> works properly ASAP (given that this name is fairly localized in the
> code base)

Because Windows is supposed to be able to work with this.

> "wc.svn" for instance? For migration purposes, both .svn and wc.svn
> could be supported for a while.

Please, no! I truly like the fact that my working copies aren't
cluttered with another visible directory at every single level.

-- 
Jamin W. Collins
This is the typical unix way of doing things: you string together lots
of very specific tools to accomplish larger tasks. -- Vineet Kumar
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org