path: root/LOCKS
Commit message (Collapse)AuthorAgeFilesLines
* Explicitly require Security Officer's approval for kernel PRNG bits.trasz2013-09-171-0/+4
| | | | | | | | | Note that there is ongoing discussion about approval requirement for userland PRNG bits. Reviewed by: so (des) Approved by: core (jhb) Approved by: re (gjb)
* Test commit to make sure commit mail works after moving the server.peter2012-12-291-0/+1
| | | | Approved by: core (implicit)
* Update LOCKS syntax.peter2008-06-051-4/+4
| | | | Approved by: core (implicit)
* Once the release goes out, RELENG_7_* will need approval from so@.cperciva2008-01-241-0/+1
| | | | Approved by: core (two months ago)
* Document commit constraints for RELENG_6_*.ru2006-01-131-0/+1
| | | | Approved by: core (jhb)
* Document the previously existing RELENG_[45]_* security branch locks.peter2005-06-021-0/+3
| | | | Approved by: core (quite a while ago)
* Add a 'statement of intent' blurb to the top of MAINTAINERS. Splitpeter2005-06-021-0/+8
the role of MAINTAINERS into advisory and strict parts. Introduce a new LOCKS file to document enforced locked parts of the tree. Strict locks are only added with core approval and will generally have a renewal timeout. Clarify that the source tree is a community effort, not a place to stake out 'turf'. This will be refined as needed. With-core-hat-on: Yes
OpenPOWER on IntegriCloud