Re: svn status -v

In article <44E029BE.3060809@xbc.nu>,
  Branko Èibej <brane@xbc.nu> writes:

> I agree it's a bit confusing, but it's not really wrong ... the last
> "svn status" says that d2/f was last changed in revision 1, which is
> true, because it's actually the same file as d1/f. When you committed
> the the copy of d1 to d2, the client assumed it was creating a new d2/f,
> but that's not what actually happens in the repository. The really
> confusing bit is that "svn up -r1 d2/f" will complain that d2/f doesn't
> exist in revision 1 ... but that's also true. :)

I found "svn log -r COMMITTED d2/f" causes an error.

nute% svn log -r COMMITTED d2/f
svn: File not found: revision 1, path '/d2/f'

I think it is a bug.

The last committed revision should be 2 which is the commit
for svn cp.

-- 
Tanaka Akira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org