Johan Corveleyn wrote on Sun, Apr 14, 2013 at 02:37:13 +0200:
> On Fri, Mar 8, 2013 at 4:35 PM, Stefan Zumwiese <dreimal_at_abwesend.de> wrote:
> > Am 11.02.2013 22:08, schrieb Stefan Zumwiese:
> >> When viewing the log of project1, I can see only the direct changes of
> >> project1, not the changes that were made in the relative externals.
> >>
> >> Since I'm currently deciding on the repository structure: how good are
> >> chances that something like --include-externals or
> >> --include-local-externals might be added as an option to svn log in the
> >> future?
> >
> > (Choose a name for the flag as you see fit.)
>
> Okay, might be interesting, but I'm not sure if this is easily doable
> given the current design of externals. Externals are a pure
> client-side concept ... the server just sees this as another property
> but doesn't do anything special with it. Maybe some other dev can
> comment more on this ....
You're correct, 'svn log' is about walking the history of a node (and
about showing the per-revision changed-paths info) and isn't aware of
externals. "SVN_PROP_EXTERNALS" does not occur in the server-side code.
That said, there is syntax 2 of 'svn log':
% $svn h log | head
log: Show the log messages for a set of revision(s) and/or path(s).
usage: 1. log [PATH][@REV]
2. log URL[@REV] [PATH...]
It wants a URL, but the PATH arguments can contain slashes, so a little
script can construct a correct invocation that covers cwd + externals.
(You probably want to call one of our APIs ---
svn_wc_parse_externals_description3()? --- (maybe via the bindings)
rather than re-invent svn:externals parsing.)
Daniel
Received on 2013-04-14 03:55:32 CEST