Does anybody have any further ideas regarding the below? I'd like to
be able to reorganize this project in the repository, but am worried
that I'm having to use --force on a directory that contains one
directory that's there courtesy of an external definition. Should I
be worried, or should I feel safe forcing it in this case?
On Jan 31, 2006, at 11:34, Ryan Schmidt wrote:
> I have a web site in our repository whose structure I want to
> rearrange slightly: I want to move everything that's in the trunk
> now into a new subdirectory "web." This should be easy:
>
> $ cd working-copy-of-trunk
> $ svn mkdir web
>
> Now move everything into it:
>
> $ svn mv foo web
> $ svn mv bar web
>
> etc.
>
> One directory in this project, libs, contains one externals
> definition. When I try to move libs, I get an unexpected message:
>
> $ svn mv libs web
> Performing status on external item at 'libs/some-library'
> svn: Use --force to override this restriction
> svn: Move will not be attempted unless forced
> svn: 'libs/some-library' is not under version control
>
> I tried moving the directory with --force in a test repository, and
> I didn't see any ill effects... am I overlooking a potential
> problem here, or should I feel safe in using the --force option to
> move this directory? If it's safe, I'd consider the message and the
> refusal to work without --force a bug.
>
>
> Kalin Kozhuharov asked this in November 2005 and seems to have
> gotten no response:
>
> http://svn.haxx.se/users/archive-2005-11/0011.shtml
>
>
> The behavior may have initially been introduced as a result of this
> discussion:
>
> http://svn.haxx.se/dev/archive-2004-11/0930.shtml
>
> And the resulting bug report:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=2136
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 3 12:24:06 2006