Page MenuHomeFreeBSD

Clarify wording when warning about unauthorized MFHs
ClosedPublic

Authored by grembo on Jul 19 2018, 9:34 PM.
Tags
None
Referenced Files
F171132438: D16355.diff
Tue, Sep 8, 10:00 PM
Unknown Object (File)
Sun, Aug 23, 7:32 PM
Unknown Object (File)
Sat, Aug 22, 5:56 PM
Unknown Object (File)
Sat, Aug 22, 5:56 PM
Unknown Object (File)
Sat, Aug 22, 5:55 PM
Unknown Object (File)
Jul 24 2026, 9:26 PM
Unknown Object (File)
Jul 20 2026, 11:53 PM
Unknown Object (File)
Jul 19 2026, 9:52 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
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.