Clarification for paths argument to svn_ra_get_log2

Hi!

The documentation of the paths argument to svn_ra_get_log2 is unclear to
me. Maybe it can be written to be more precise about intended use and
behaviour. A clarification here by mail would be good in any case.

1. What is the default behaviour if paths is NULL or empty?
    a) empty log, as seems to be implemented by some servers?
    b) log of current directory?
    c) full log of whole repository?

2. The paths are relative to the current session directory,
    but this description can have two possible meanings:
    a) forbid absolute paths,
       while describing how relatives paths are interpreted
    b) only describe how relative paths are interpreted,
       without saying anything at all about absolute paths
    Current assertions enforce a). Does this mean there is no way to
    access the full log of a repository while the session is for a
    subtree?

3. Are changes reported recursively? The documentation reads as if for
    directories specified as elements of the paths list, only property
    changes, additions and deletions of files would be reported. This
    seems to exclude modifications of files or subdirs. Implementations
    seem to behave differently.

The issues from 1. and 2. affect tools like bzr-svn as discussed in
https://bugs.launchpad.net/bzr-svn/+bug/235776
as well as my fix to an issue in subversion I reported recently:
http://thread.gmane.org/gmane.comp.version-control.subversion.devel/100900

I guess other commands besides svn_ra_get_log2 which accept (relative)
paths might be affected in a similar way.

Greetings,
  Martin von Gagern