-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix the license at the top of the source code files #35
Conversation
…bute them to the Falco Authors Signed-off-by: Loris Degioanni <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM label has been added. Git tree hash: e6de64c57507dd57def75805246fa69f0c896364
|
/approve |
/approve |
@leogr: Unable to find goose. Have you checked the garden? In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leogr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
license is now properly attributed to the Falco Authors, reflecting the main repository license file.
Signed-off-by: Loris Degioanni [email protected]
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area build
/area driver-kmod
/area driver-ebpf
/area libscap
/area libsinsp
What this PR does / why we need it:
Which issue(s) this PR fixes:
Even if the COPYING file in the repository correctly attributes the license to the Falco Authors, the license headers at the beginning of the source files have not been updated yet to reflect that. This PR fixes the inconsistency.
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE