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)
Sat, Oct 11, 6:49 AM
Unknown Object (File)
Sat, Oct 11, 6:35 AM
Unknown Object (File)
Thu, Oct 9, 9:57 PM
Unknown Object (File)
Sep 15 2025, 5:43 AM
Unknown Object (File)
Sep 13 2025, 10:26 PM
Unknown Object (File)
Aug 11 2025, 3:14 PM
Unknown Object (File)
Aug 3 2025, 2:46 PM
Unknown Object (File)
Jun 24 2025, 4:02 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.