Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The lack of a author or date is not a sign of a permissions problem. The lack of a log message may be a sign of a permissions problem.</p> <p>First of all Subversion does not actually require the svn:author, svn:date or svn:log properties actually be set to anything. In general you won't end up with a commit without a svn:author or svn:date empty unless someone has removed the properties with the propdel command (e.g. <code>svn propdel svn:author --revprop -r 1234 $URL</code>). Subversion tries to encourage you to leave a log message but you can also give it a blank one unless that's limited by commit hooks. So it's entirely possible that someone intentionally made those changes to the revision. This also means that any tools you're using to process Subversion commits should be able to handle the lack of these values.</p> <p>With respect to permissions if you're using path based authorization (authz-db with svnserve or AuthzSVNAccessFile with httpd) then your access to the paths modified by the revision may limit what you can see.</p> <p>In particular:</p> <ul> <li>If you have access to all paths you'll see anything you ask for including all the changed paths and all the revision properties.</li> <li>If you have access to only some paths you'll only see the changed paths you have access to listed when using -v and only the svn:author and svn:date revision properties. svn:log will be hidden since it may contain the names of the files you don't have access to. Other revision properties (even custom ones) will be omitted as well.</li> <li>If you have no access to any of the paths changed by the revision then the revision will be omitted entirely from the output of log.</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload