title: hg access control to central repository
body: <p>We come from a subversion background where we have a QA manager who gives commit rights to the central repository once he has verified that all QC activities have been done. </p>
  
  <p>Me and a couple of colleagues are starting to use mercurial, and we want to have a shared repository that would contain our QC-ed changes. Each of the developers hg clones the repository and pushes his changes back to  the shared repository. I've read the HG init tutorial and skimmed through the red bean book, but could not find how to control who is allowed to push changes to the shared repository. </p>
  
  <p>How would our existing model of QA-manager controlled commits translate to a mercurial 'central' repository?</p>