History log of /freebsd-10-stable/LOCKS
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
# 256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

# 255635 17-Sep-2013 trasz

Explicitly require Security Officer's approval for kernel PRNG bits.

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)


# 244822 29-Dec-2012 peter

Test commit to make sure commit mail works after moving the server.

Approved by: core (implicit)


# 179574 05-Jun-2008 peter

Update LOCKS syntax.

Approved by: core (implicit)


# 175650 24-Jan-2008 cperciva

Once the release goes out, RELENG_7_* will need approval from so@.

Approved by: core (two months ago)


# 154289 13-Jan-2006 ru

Document commit constraints for RELENG_6_*.

Approved by: core (jhb)


# 146891 02-Jun-2005 peter

Document the previously existing RELENG_[45]_* security branch locks.

Approved by: core (quite a while ago)


# 146890 02-Jun-2005 peter

Add a 'statement of intent' blurb to the top of MAINTAINERS. Split
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