On 24.02.2013 18:21, Gabriela Gibson wrote:
> 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?
"svn diff" on which target? :)
If I run your command on the root of a trunk checkout, the result is
empty, as expected, since there are no trunk changes in there. However,
if I say,
svn diff -c 965054 ^/
in the same directory, or
svn diff -c 965054 http://svn.apache.org/repos/asf/
anywhere at all, I get a result.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
