[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn status -v

From: Branko Čibej <brane_at_xbc.nu>
Date: 2006-08-18 10:56:41 CEST

Tanaka Akira wrote:
> 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.
That's the last committed revision for d2. d2/f is the same object as
d1/f, and it wasn't changed in revision 2.

The real question here is: do we want to expose the fact that the FS is
a DAG to users like this? I have no problem with it, but it can be
confusing, as this conversation shows.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 18 10:56:47 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.