src/LOCKS, branch upstream/13.1.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=upstream%2F13.1.0 2018-06-09T03:08:04Z LOCKS: update current locks 2018-06-09T03:08:04Z Eitan Adler eadler@FreeBSD.org 2018-06-09T03:08:04Z urn:sha1:fcb667426a7e0a4ecf7e3be661f770f4b77352bc - use a wild card for releng instead of listing them out. This ignores a technicality that re@ owns the branches during release cycles, but this has not been document in this file in a long time (if ever). Approved by: core Explicitly require Security Officer's approval for kernel PRNG bits. 2013-09-17T14:19:05Z Edward Tomasz Napierala trasz@FreeBSD.org 2013-09-17T14:19:05Z urn:sha1:bb53d809a42d00121a6bbb56f7d4289082a197a9 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. 2012-12-29T16:03:23Z Peter Wemm peter@FreeBSD.org 2012-12-29T16:03:23Z urn:sha1:ec26457ccb8aba01ac54f2b8f50fd60c9fff95fa Approved by: core (implicit) Update LOCKS syntax. 2008-06-05T19:47:58Z Peter Wemm peter@FreeBSD.org 2008-06-05T19:47:58Z urn:sha1:8d958254858f8bca64072796b82dd6aa371cf493 Approved by: core (implicit) Once the release goes out, RELENG_7_* will need approval from so@. 2008-01-24T22:07:03Z Colin Percival cperciva@FreeBSD.org 2008-01-24T22:07:03Z urn:sha1:639c89833a9b93431af79952e906b3a9fe15722e Approved by: core (two months ago) Document commit constraints for RELENG_6_*. 2006-01-13T06:51:43Z Ruslan Ermilov ru@FreeBSD.org 2006-01-13T06:51:43Z urn:sha1:a59bcb144a74b5ada2a0e15a9beaef5e76b6922e Approved by: core (jhb) Document the previously existing RELENG_[45]_* security branch locks. 2005-06-02T22:57:30Z Peter Wemm peter@FreeBSD.org 2005-06-02T22:57:30Z urn:sha1:d97f4741a4b38b60a8faa1eb0ff456fd6cfdc2d1 Approved by: core (quite a while ago) Add a 'statement of intent' blurb to the top of MAINTAINERS. Split 2005-06-02T21:28:33Z Peter Wemm peter@FreeBSD.org 2005-06-02T21:28:33Z urn:sha1:072f68a7c479c803fba07c80411aef06f3ba085f 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