Jörg Eichhorn <eichhorn@ponton-consulting.de> wrote on 10/24/2006 04:24:30
AM:
> i experienced a strange behavior when commiting a file in a folder (e.g.
> 'folder1') which was created, added to the repository (but not commited)
> and renamed (renamed to 'folder2').
> This new file is committed to the repository in the folder named like it
> was added to the repository ('folder1'). On the local filesystem the
> folder is renamed, but it looks like that this change is not passed to
> svn, even the svn log show some operation:
>
> add-N D:\src\project\folder1
> A D:/src/project/folder1
> delete --force D:/src/project/folder1
> D D:/src/project/folder1
> add -N D:\src\project\folder2\file
> A D:/src/project/folder2/file
> commit -m "foobar" -N D:/src/project/folder2
> Adding D:/src/project/folder2
> Committed revision 18.
> commit -m "foobar" D:/src/project/folder2/file
> Adding D:/src/project/folder2/file
> Transmitting file data ...
> Committed revision 19.
Subversion does not allow an added file to moved/renamed (this is finally
fixed in trunk/1.5). If you truly wanted the history of the file to show
a move, you would have to commit the original add, at which point it could
then be renamed. This is even true in trunk. All it fixes, is that it
allows the item to be moved, but since it was never committed there would
still be no history of the move.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Oct 24 14:58:48 2006