> Ryan Schmidt wrote:
>
>> Exactly, Matt. The only reason I can think of why one would care
>> where Subversion stores its admin directories is that one is copying
>> and moving files using native OS commands instead of using svn cp and
>> svn mv. And that would be a user error. One must use svn cp and svn
>> mv. The book goes into it in some detail and there's also a relevant
>> FAQ entry:
>
> BUZZ. Incorrect assumption. You totally neglect 3rd party CLOSED
> SOURCE applications that may manipulate data however they see fit.
> The
> meta data is often a casualty.

That... is of course a good point. And you're right, I do tend to
forget that point, as I haven't been versioning such data much. But
this has bitten me on one .rtfd file I version, which gets borked
every time I change and save it in TextEdit. It is a happy side-
effect that moving the meta-data out of the individual directories
would fix part of the opaque collection issue:

> Also, implicit in this discussion is just the general fragility of the
> meta-data to begin with. I can't even begin to list the number of
> hoops
> I've had to jump through to repair a working copy *without starting
> from
> scratch*. From what I've been reading 1.5 may help with some of that.
>
> Having the ability to remove the metadata from the working copy
> would be
> absolutely brilliant IMO. A number of VC tools seem to get by with
> this.