On 9/8/06, tommyjb@gmail.com <tommyjb@gmail.com> wrote:
> C:\test>svn co file:///c:/svn/trunk .
> A b.txt
> A a.txt
> Checked out revision 30.
>
> C:\test>svn rm file:///c:/svn/trunk/b.txt -m "Deleted on server side."
>
> Committed revision 31.
>
> C:\test>svn rm b.txt
> D b.txt
>
> C:\test>svn ci -m "Deleted on client side."
> Deleting b.txt
>
> Committed revision 32.
>
> C:\test>svn log -r 32:31 -v file:///c:/svn/
> ------------------------------------------------------------------------
> r32 | Tom | 2006-09-09 02:40:05 +0100 (Sat, 09 Sep 2006) | 1 line
> Changed paths:
>
> Deleted on client side.
> ------------------------------------------------------------------------
> r31 | Tom | 2006-09-09 02:39:52 +0100 (Sat, 09 Sep 2006) | 1 line
> Changed paths:
> D /trunk/b.txt
>
> Deleted on server side.
> ------------------------------------------------------------------------
>
> C:\test>svn di -r 31:32 file:///c:/svn/
>
> C:\test>
This is known, and IIRC was discussed on this list fairly recently.
It's kinda weird, but I believe that's intentional behavior. We don't
error out on a delete of an already deleted item, and it is possible
to have empty commits, although nontrivial to actually make it happen
via the client.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 11 15:19:23 2006