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

Re: svn log "hangs"

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-11-06 02:45:49 CET

On Nov 5, 2004, at 5:35 PM, Dominic Anello wrote:
> In fact, I kind of regard it as a misfeature
> that one of my users might not be able to see the full history of a
> file
> because it happens to share a revision with another file they don't
> have
> access to.

I think you guys are misunderstanding the security feature here.

 From the authz_policy document:

      * If a revision returned by 'svn log' contains a mixture of
        readable/unreadable changed-paths, then the log message is
        suppressed, along with the unreadable changed-paths. Only the
        revision number, author, date, and readable paths are

      * If a revision returned by 'svn log' contains only unreadable
        changed-paths, then only the revision number is displayed.

So, if by some chance a public and private file are both changed in the
same commit (not a practice we recommend, but not always avoidable
either), then you don't outright "lose the history" of the public file.
  'svn log public_file' still returns all the revisions in which the
public file changed. You can even see the date and author on the
naughty revision. The only thing that will be suppressed is the
naughty revision's log message, and the fact that the private file was

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 6 02:47:34 2004

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

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