It does not solve the complete problem.
Indeed, my description was a simplified case.
We had the problem that a directory was deleted,
and a new directory having the same name was added.
Because of this, the update failed; the new directory
could not be updated to the wc.
svn must at least rename the old directory to something new.
> Folker Schamel <schamel23@spinor.com> writes:
>
>
>>Yes, exactly!!!
>>Thanks for your sample!
>>
>>I also would be interested into feedback from a svn team member.
>>Should I add it to the issue tracker?
>
>
> Yes. But it shouldn't have any such proposal about an 'svn:temporary'
> property. It should say:
>
> Summary: orphaned unversioned files should not be an errorful state
>
> Description: 'svn up' shouldn't give an error when failing to
> remove a deleted directory simply because it contains unversioned
> files -- it should simply give a notification like "WARNING: Left
> tree of unversioned objects at 'path/to/deleted/dir'"
>
> I mean, isn't it enough to see the following:
>
> $ svn up
> M Makefile
> A new_module
> A new_module/main.c
> A new_module/util.c
> D old_module
> WARNING: Left tree of unversioned objects at 'old_module'
> A another_new_module
> A another_new_module/main.c
> ...
> Updated to revision 453.
> $
>
> Then:
>
> $ svn st
> ? old_module
> $
>
> ??
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 18 18:53:48 2003