On Mon, 2004-06-28 at 10:28, Jeff Squyres wrote:
> 1. An persistently incorrect error message (i.e., reporting the error in
> the incorrect directory).
>
> 2. The fact that "svn up" stops after this error (which you indicated in
> an earlier post has been fixed for svn 1.1).
>
> So I think all of our confusion we because of #1. If you recall, my
> prior posts were about svn complaining about the "src/mca" directory,
> and you hypothesized that it was because svn was trying to remove and
> re-create the src/mca directory, but I said that this should not be
> possible -- the src/mca directory had not changed in quite a while.
>
> But the directories below src/mca *had* changed. Hence, it wasn't
> src/mca that was the problem -- it was something deeper under the
> src/mca tree; we were looking in the wrong place.
>
> Does this all make sense?
Wow, Jeff, nice analysis!
And now, here's the news: we're in process of freezing code for an svn
1.1 release. In svn 1.1, 'svn up' no longer stops dead in its tracks
when it tries to remove a directory that contains unversioned stuff. It
just leaves the unversioned stuff behind, and keeps going. This should,
for all practical purposes, solve all the pain you've been
experiencing. My recommendation, in fact, is that you checkout a copy
of svn's /trunk code and try it out today.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 29 00:34:22 2004