[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Clarification for paths argument to svn_ra_get_log2

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 03 Jun 2008 11:05:52 -0400

Martin von Gagern wrote:
> Resending, as I forgot to cc the list... sorry.
>
> C. Michael Pilato wrote:
> | I seem to recall that recently I realized that NULL and empty had two
> | different interpretations in 'svn log'. I think empty resulted in (b),
> | and (a surprise to me) NULL in (c).
>
> If that is indeed the case and intended this way, it would certainly
> merit documentation.

Okay, looking in svn_repos_get_logs4(), the code does the following pretty
early:

   if (! paths)
     paths = apr_array_make(pool, 0, sizeof(const char *));

So it would seem that NULL and empty have the same meaning.

> |> 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?
> |
> | That is correct.
>
> If what you just wrote is true, then passing NULL would be just such a
> way to access the full log. Or did I misunderstand something?

I think it turns out to be false, though.

> | If you need to do something at a different location, you
> | can use svn_ra_reparent() to change the current session URL.
>
> One of the bzr devs, Jelmer Vernooij, argued that changing URL is often
> not an option due to access restrictions.

As I think I said already (but maybe in private mail?), if changing the URL
to a shorter (higher-pathed) one is no good due to access restrictions,
wouldn't those same access restrictions get in the way of us reporting logs
for those higher-level directories anyway?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-06-03 17:06:06 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.