Gabriela Gibson wrote on Sun, Feb 24, 2013 at 17:21:13 +0000:
> On 22/02/13 00:45, Daniel Shahaf wrote:
> >How about just linking to a revnum wherein a standalone application was
> >added? That's less likely to get out of date.
> >
> >For example
> >
> >% svn log -qv -l1 -r 1:HEAD subversion/tests/cmdline/atomic-ra-revprop-change.c
> >------------------------------------------------------------------------
> >r965054 | danielsh | 2010-07-17 14:23:38 +0300 (Sat, 17 Jul 2010)
> >Changed paths:
> > M /subversion/branches/atomic-revprop/build.conf
> > M /subversion/branches/atomic-revprop/subversion/tests/cmdline
> > A /subversion/branches/atomic-revprop/subversion/tests/cmdline/atomic-ra-revprop-change.c
> > ...
> >------------------------------------------------------------------------
> >
>
> when I then try: svn diff -c 965054 I get a silent failure.
>
> However,
>
> svn blame subversion/tests/cmdline/atomic-ra-revprop-change.c
>
> clearly shows that the revision 965054 has contents.
>
> What is going on?
>
You're probably running the command in a working copy of
/subversion/trunk. That node did not change in r965054:
% svn log -r 965054:1 -q -l 1 | sed -ne '/^r/ s/ .*//p'
r965025
so you get, properly, no output and exit code zero. ('svn di -c
1000000' would do this too.) Try:
% svn diff -c r965054 ^/subversion
Received on 2013-02-25 13:36:14 CET