Dietrich Epp <dietrich@zdome.net> writes:
> I don't consider it a problem in Interface Builder. It's just
> something that Interface Builder does that Subversion doesn't
> understand yet. Someday:
>
> svn propset svn:volatile yes *.nib
>
> And I didn't say it was a bug in subversion... but you saw what I
> typed, and you saw what it did. For all I know it was a memory error.
> All I know is that a directory with a handful of files suddenly had
> only one after I committed.
Dietrich, I'm going to have to call you on that one. Your first mail
said:
"I can't even figure out why the files disappeared in the first
place, but I do know that Subversion is entirely to blame."
Now later, after admitting that what probably happened is that
Interface Builder *destroyed Subversion's metadata*, you still feel
that Subversion is "entirely to blame"??
Why, instead, can't Interface Builder notice the presence of data that
it didn't generate, and preserve it? Note that Interface Builder had
the same problem with CVS/ subdirs, and (if I recall correctly) IB
eventually added code to treat them specially. The same thing may
happen with .svn/ directories someday. Or maybe Subversion will learn
to store metadata differently in the future.
But right now, Subversion assumes that its .svn/ areas won't be
destroyed. That's part of the environmental requirements for using
it. If you don't have that kind of environment, then don't use it.
Bad User Experience != Bug,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 16 23:42:23 2003