On May 20, 2006, at 10:28, Sergio Bossa wrote:
> $ svnadmin create test
>
> $ svn co file:///path/to/test
>
> $ cd test
>
> $test> mkdir a_dir
>
> $test> svn add a_dir
>
> $test> svn commit -m ""
>
> $test> cd a_dir
>
> $a_dir> touch test_file
>
> $a_dir> svn add test_file
>
> $a_dir> svn commit -m ""
>
> $a_dir> mv test_file test_file_rn
>
> $a_dir> svn remove test_file
>
> $a_dir> svn add test_file_rn
I don't know why you're moving a version-controlled file out from
under Subversion's nose (test_file), then deleting the now-
nonexistent file Subversion thinks is still there, then adding
(without history) the file under its new name. If it's just a setup
for the behavior below, then fine, but I can't imagine why you
wouldn't in real use replace the above three commands with "svn mv
test_file test_file_rn".
> $a_dir> svn commit -m ""
>
> $a_dir> cd ..
To avoid the problem below, you will want to do an "svn update" at
this point.
> $test> mkdir new_dir
>
> $test> svn add new_dir
>
> $test> svn move a_dir new_dir/a_dir
> A new_dir/a_dir
> D a_dir/test_file_rn
> D a_dir
>
> $test> svn status
> A new_dir
> A + new_dir/a_dir
> D + new_dir/a_dir/test_file
> D a_dir
> D a_dir/test_file_rn
>
> Here is the problem:
>
> D + new_dir/a_dir/test_file
>
> Now I'm using Subversion 1.3.0 on SuSE Linux 10.
>
> Hope this helps in clarifying.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 20 16:06:07 2006