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, Mar 29, 12:26 PM
Unknown Object (File)
Dec 20 2023, 3:43 AM
Unknown Object (File)
Nov 30 2023, 3:27 PM
Unknown Object (File)
Nov 23 2023, 3:38 AM
Unknown Object (File)
Nov 19 2023, 1:51 AM
Unknown Object (File)
Nov 19 2023, 1:51 AM
Unknown Object (File)
Nov 19 2023, 12:24 AM
Unknown Object (File)
Nov 4 2023, 11:36 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.