History log of /freebsd/LOCKS (Results 1 – 24 of 24)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 08ae2653 26-Dec-2023 Minsoo Choo <minsoochoo0122@proton.me>

Update LOCKS for Git

Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me>
Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/937


Revision tags: release/14.0.0
# 05248206 16-Aug-2023 Warner Losh <imp@FreeBSD.org>

Remove $FreeBSD$: one-line bare tag

Remove /^\s*\$FreeBSD\$$\n/


Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0
# fcb66742 09-Jun-2018 Eitan Adler <eadler@FreeBSD.org>

LOCKS: update current locks

- 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

LOCKS: update current locks

- 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

show more ...


Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0
# 0bfd163f 18-Oct-2013 Gleb Smirnoff <glebius@FreeBSD.org>

Merge head r233826 through r256722.


# 3caf0790 13-Oct-2013 Simon J. Gerraty <sjg@FreeBSD.org>

Merge head@256284


# 1ccca3b5 10-Oct-2013 Alan Somers <asomers@FreeBSD.org>

IFC @256277

Approved by: ken (mentor)


# 27650413 02-Oct-2013 Mark Murray <markm@FreeBSD.org>

MFC - tracking update.


Revision tags: release/9.2.0
# ef90af83 20-Sep-2013 Peter Grehan <grehan@FreeBSD.org>

IFC @ r255692

Comment out IA32_MISC_ENABLE MSR access - this doesn't exist on AMD.
Need to sort out how arch-specific MSRs will be handled.


# bb53d809 17-Sep-2013 Edward Tomasz Napierala <trasz@FreeBSD.org>

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

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)

show more ...


# cfe30d02 19-Jun-2013 Gleb Smirnoff <glebius@FreeBSD.org>

Merge fresh head.


Revision tags: release/8.4.0
# d241a0e6 26-Feb-2013 Xin LI <delphij@FreeBSD.org>

IFC @247348.


# d9a44755 08-Feb-2013 David E. O'Brien <obrien@FreeBSD.org>

Sync with HEAD.


# 46b1c55d 04-Jan-2013 Neel Natu <neel@FreeBSD.org>

IFC @ r244983.


# ec26457c 29-Dec-2012 Peter Wemm <peter@FreeBSD.org>

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

Approved by: core (implicit)


Revision tags: release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0
# 8d958254 05-Jun-2008 Peter Wemm <peter@FreeBSD.org>

Update LOCKS syntax.

Approved by: core (implicit)


Revision tags: release/7.0.0_cvs, release/7.0.0
# 639c8983 24-Jan-2008 Colin Percival <cperciva@FreeBSD.org>

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

Approved by: core (two months ago)


Revision tags: release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0
# a59bcb14 13-Jan-2006 Ruslan Ermilov <ru@FreeBSD.org>

Document commit constraints for RELENG_6_*.

Approved by: core (jhb)


Revision tags: release/6.0.0_cvs, release/6.0.0
# d97f4741 03-Jun-2005 Peter Wemm <peter@FreeBSD.org>

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

Approved by: core (quite a while ago)


# 072f68a7 02-Jun-2005 Peter Wemm <peter@FreeBSD.org>

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.

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

show more ...


Revision tags: release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0
# 8d958254 05-Jun-2008 Peter Wemm <peter@FreeBSD.org>

Update LOCKS syntax.

Approved by: core (implicit)


Revision tags: release/7.0.0_cvs, release/7.0.0
# 639c8983 24-Jan-2008 Colin Percival <cperciva@FreeBSD.org>

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

Approved by: core (two months ago)


Revision tags: release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0
# a59bcb14 13-Jan-2006 Ruslan Ermilov <ru@FreeBSD.org>

Document commit constraints for RELENG_6_*.

Approved by: core (jhb)


Revision tags: release/6.0.0_cvs, release/6.0.0
# d97f4741 03-Jun-2005 Peter Wemm <peter@FreeBSD.org>

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

Approved by: core (quite a while ago)


# 072f68a7 02-Jun-2005 Peter Wemm <peter@FreeBSD.org>

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.

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

show more ...