Mercurial > kallithea
view docs/usage/locking.rst @ 3574:000653f7cdf9 beta
avoid displaying repr of internal classes in user facing messages
The context of the message will tell where the problem was and there is no reason to show
... does not exist for this repository <MercurialRepository at /home/marcink/repos/rhodecode>
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Thu, 21 Mar 2013 11:17:01 +0100 |
parents | 8b8edfc25856 |
children | e73a69cb98dc |
line wrap: on
line source
.. _locking: =================================== RhodeCode repository locking system =================================== | Repos with **locking function=disabled** is the default, that's how repos work today. | Repos with **locking function=enabled** behaves like follows: Repos have a state called `locked` that can be true or false. The hg/git commands `hg/git clone`, `hg/git pull`, and `hg/git push` influence this state: - The command `hg/git pull <repo>` will lock that repo (locked=true) if the user has write/admin permissions on this repo - The command `hg/git clone <repo>` will lock that repo (locked=true) if the user has write/admin permissions on this repo RhodeCode will remember the user id who locked the repo only this specific user can unlock the repo (locked=false) by calling - `hg/git push <repo>` every other command on that repo from this user and every command from any other user will result in http return code 423 (locked) additionally the http error includes the <user> that locked the repo (e.g. “repository <repo> locked by user <user>”) So the scenario of use for repos with `locking function` enabled is that every initial clone and every pull gives users (with write permission) the exclusive right to do a push. Each repo can be manually unlocked by admin from the repo settings menu.