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

Re: [Issue 1061] Changed - 'svn diff URL ADDED_FILE' not yet supported

From: <cmpilato_at_collab.net>
Date: 2003-04-18 05:44:54 CEST

Robert Pluim <rpluim@bigfoot.com> writes:

> issues@subversion.tigris.org writes:
> > +
> > + ------- Additional Comments From cmpilato@tigris.org 2003-04-17 15:07 PDT -------
> > + This seems to work fine now. Dunno why. Removed the "unsupported
> > + feature" error in revision 5665.
> > \ No newline at end of file
>
> Bizarre. This used to fail for me in the depths of
> svn_wc_crawl_revisions. All right, who's been fixing bugs without
> telling us?

Code churns quite fast in this product... coulda been anyone! :-)

> svn diff doesn't quite work the way I expect though. tags/testtag is
> an 'svn cp' of rev 37, committed at rev 39.
>
> $ svn diff file:///home/rpluim/testrepo/tags/testtag/1000 1000_at_38
> svn: Filesystem has no item
> svn: 'file:///home/rpluim/testrepo/tags/testtag/1000' at rev 38 wasn't found in repository.
>
> ? Why is it using the rev of the second target here?

Under-the-hood, "1000" is being converted to "the URL of '1000'". I
know, that doesn't seem to be documented in 'svn help diff', but...

> I could agree that 1000@38 is illegal syntax, however:
>
> $ svn diff file:///home/rpluim/testrepo/tags/testtag/1000 file:///home/rpluim/testrepo/trunk/foo/1000_at_38
> svn: Filesystem has no item
> svn: 'file:///home/rpluim/testrepo/tags/testtag/1000' at rev 38 wasn't found in repository.
>
> I thought that not specifying the rev => HEAD?

This looks like it might be a different bug. Perhaps sussman has an
idea of what's happening here?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 18 05:47:57 2003

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.