Page MenuHomeFreeBSD

Clarify wording when warning about unauthorized MFHs
ClosedPublic

Authored by grembo on Jul 19 2018, 9:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jan 9, 8:18 AM
Unknown Object (File)
Thu, Jan 8, 8:14 PM
Unknown Object (File)
Wed, Jan 7, 1:13 PM
Unknown Object (File)
Tue, Jan 6, 12:10 PM
Unknown Object (File)
Thu, Jan 1, 1:22 PM
Unknown Object (File)
Thu, Dec 25, 7:16 AM
Unknown Object (File)
Tue, Dec 23, 5:45 AM
Unknown Object (File)
Oct 26 2025, 5:09 PM
Subscribers

Details

Summary

The previous wording was quite confusing (to me), as it's after listing
all blanket approvals that allow MFHing without explicit approval
by ports-sectam/portmgr and introduced the term "unauthorized commit".

As this now happened the second time to me, I changed the wording
so that it's easier to understand in context ("what am I allowed to commit
without waiting for approval"), but still carrying the important message
that MFHing things that are not covered by a blanket requires explicit
approval by the respective teams.

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 18181
Build 17914: arc lint + arc unit

Event Timeline

adamw added a subscriber: adamw.

That is definitely much clearer. Thanks!

This revision is now accepted and ready to land.Jul 19 2018, 11:59 PM
This revision was automatically updated to reflect the committed changes.