Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Just for other readers less familiar with <code>VREF</code> (introduced with <a href="http://sitaramc.github.com/gitolite/master-toc.html" rel="nofollow">"g3" or Gitolite V3</a>).</p> <p>The idea behind <a href="http://sitaramc.github.com/gitolite/vref.html#vref-fallthru" rel="nofollow">VREF rules</a> are:</p> <blockquote> <ul> <li>For every refex starting with <code>VREF/FOO/</code> in a rule that applies to this user, a call to a program called <code>FOO</code> is triggered. Note that the program isn't even called if the <code>VREF</code> rule doesn't apply to that user.</li> </ul> </blockquote> <p>This is why one can define an '<code>update</code>' hook even though the <a href="http://sitaramc.github.com/gitolite/cust.html#hooks" rel="nofollow"><code>update</code> hook is reserved by gitolite</a>.<br> A normal <code>update</code> hook expects 3 arguments (ref, old SHA, new SHA).<br> Any VREF will get those three, followed by at least 4 more. Your '<code>update</code>' VREF should just ignore the extra args.</p> <blockquote> <ul> <li><strong><a href="http://foldoc.org/fallthru" rel="nofollow">fallthru</a></strong> is considering success (ie you won't be denied a git operation on a repo because none of the VREF applied)<br> If fallthru were to be considered 'failure', you'd be forced to add a "success rule" like this for every vref you used in this repo, in each case listing every user who was not already mentioned in the context of that vref</li> </ul> </blockquote> <p>Considering the <code>update</code> VREF program, you could add a parameter which would allow your update script to recognize it is called in the <code>gitolite-admin</code> context (and should do nothing):</p> <pre><code>repo gitolite-admin - VREF/update/donothing = @all repo @all - VREF/update = @all </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POGitolite Update Hook exclude a repository
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGitolite Update Hook exclude a repository
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COLooks like this will work - was hoping for something cleaner but this makes sense
      singulars
      1. PO
      1. USN V
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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