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)
Wed, May 20, 9:52 PM
Unknown Object (File)
Wed, May 20, 2:07 AM
Unknown Object (File)
Mon, May 18, 5:39 PM
Unknown Object (File)
Mon, May 18, 2:49 PM
Unknown Object (File)
Sun, May 17, 7:33 AM
Unknown Object (File)
Tue, May 5, 12:29 PM
Unknown Object (File)
Feb 27 2026, 8:34 AM
Unknown Object (File)
Feb 19 2026, 9:41 AM
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
Lint Not Applicable
Unit
Tests Not Applicable

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.