Also, note that all the '-r' / '-c' syntaxes are directly related to peg revisions --- they are always interpreted relative to some peg revision (which, in this case, is the implicit "BASE" peg provided by svn_opt_push_implicit_dot_target())
Branko Čibej wrote on Sun, Feb 24, 2013 at 19:34:06 +0100: > On 24.02.2013 19:14, Gabriela Gibson wrote: > > On 24/02/13 17:57, Branko Čibej wrote: > >> On 24.02.2013 18:21, Gabriela Gibson wrote: > > > >> "svn diff" on which target? :) > >> > > > > Well, "svn diff -c 858288" works great, so I assumed that it's legit :> > > > > (now I have to wonder _why_ this works, heh) > > > >> 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, > > > > Hmm, why should svn care about current changes and where I am when I > > ask it to show me the changes of revision n? > > Becuase it knows how to filter the results based on given paths or URLs, > so that you can request a diff of the changes on just one file in a > particular revision, even if several files were affected. If you don't > give it a target, it uses the current path in the current working copy > as a filter. > > -- Brane > > -- > Branko Čibej > Director of Subversion | WANdisco | www.wandisco.com >
