Files
@ bb9ef0638069
Branch filter:
Location: kallithea/docs/usage/locking.rst - annotation
bb9ef0638069
1.3 KiB
text/prs.fallenstein.rst
Update CodeMirror CSS and Javascript files to version 3.15, under MIT-permissive license.
These files are exactly as they appear the upstream release 3.15 of
Codemirror, which was released under an MIT-permissive license. To extract
these files, I did the following:
I downloaded the following file:
http://codemirror.net/codemirror-3.15.zip
with sha256sum of:
$ sha256sum codemirror-3.15.zip
8cf3a512899852fd4e3833423ea98d34918cbf7ee0e4e0b13f8b5e7b083f21b9 codemirror-3.15.zip
And extracted from it the Javascript and CSS files herein committed, which
are licensed under the MIT-permissive license, placing them into their
locations in: rhodecode/public/{css,js}/
Using the procedure above, the only difference found between these files in
RhodeCode 2.2.5 release and herein were a few comments and whitespace.
Note that the file .../public/js/mode/meta_ext.js does *not* appear to be
part of CodeMirror and therefore is not included in this commit.
These files are exactly as they appear the upstream release 3.15 of
Codemirror, which was released under an MIT-permissive license. To extract
these files, I did the following:
I downloaded the following file:
http://codemirror.net/codemirror-3.15.zip
with sha256sum of:
$ sha256sum codemirror-3.15.zip
8cf3a512899852fd4e3833423ea98d34918cbf7ee0e4e0b13f8b5e7b083f21b9 codemirror-3.15.zip
And extracted from it the Javascript and CSS files herein committed, which
are licensed under the MIT-permissive license, placing them into their
locations in: rhodecode/public/{css,js}/
Using the procedure above, the only difference found between these files in
RhodeCode 2.2.5 release and herein were a few comments and whitespace.
Note that the file .../public/js/mode/meta_ext.js does *not* appear to be
part of CodeMirror and therefore is not included in this commit.
aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 aa17c7a1b8a5 8b8edfc25856 | .. _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.
|