Page MenuHomeFreeBSD

MAC/do: Rename rule_is_valid() => rule_applies()
AcceptedPublic

Authored by olce on Fri, Nov 15, 5:06 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 19, 6:24 PM
Unknown Object (File)
Tue, Nov 19, 12:56 AM
Unknown Object (File)
Mon, Nov 18, 9:40 PM
Unknown Object (File)
Mon, Nov 18, 6:32 PM
Unknown Object (File)
Mon, Nov 18, 5:29 PM
Unknown Object (File)
Sun, Nov 17, 11:54 PM
Unknown Object (File)
Sun, Nov 17, 11:52 PM
Unknown Object (File)
Sat, Nov 16, 6:26 AM

Details

Reviewers
bapt
Summary

This revision is part of a series. Click on the Stack tab below to see the context.
This series has also been squeezed into D47633 to provide an overall view.

Commit message:
This function checks whether a rule applies in the current context, i.e., if the subject's users/groups match that of the rule.
By contrast, it doesn't check if the rule as specified by the user is valid (i.e., consistent).

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 60583
Build 57467: arc lint + arc unit

Event Timeline

olce requested review of this revision.Fri, Nov 15, 5:06 PM

Commit message should explain why something was done not (just) what; in this case it the reason is fairly clear from context but still needs the reader to look at the change and understand.

agreed with @emaste on the why I personnally find rule_is_valid easier to understand then rule_applies, but still find rule_applies clear enough so I am ok with the change itself

Commit message should explain why something was done not (just) what; in this case it the reason is fairly clear from context but still needs the reader to look at the change and understand.

Of course. I just thought that this was obvious here (and the diff is tiny). Will add to the description.

This revision is now accepted and ready to land.Tue, Nov 19, 8:45 AM