Skip to content
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

[WIP] Revision of the copyright statement (revoke of PR#157) #176

Closed
wants to merge 1 commit into from

Conversation

MoonkiHong
Copy link
Contributor

Signed-off-by: MoonkiHong moonki1.hong@samsung.com

Description

As reported by issue #175, this is the PR to resolve the copyright statement issue to present the latest source codes from coconut relesae w.r.t. the guideline from LF Edge other projects.

Fixes #175

Type of change

Please delete options that are not relevant.

  • Copyright statement update, so no operational impact

How Has This Been Tested?

Pass through an embedded automated build test from GitHub. No operational change due to the fact that this PR only revised the copyright statement in comments.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • My changes generate no new warnings

Signed-off-by: MoonkiHong <moonki1.hong@samsung.com>

As reported by issue lf-edge#175, this is the PR to resolve the copyright statement issue to present the latest source codes from `coconut` relesae w.r.t. the guideline from LF Edge other projects.
@MoonkiHong MoonkiHong self-assigned this Nov 13, 2020
@MoonkiHong MoonkiHong changed the title Revision of the copyright statement (revoke of PR#157) [WIP] Revision of the copyright statement (revoke of PR#157) Nov 13, 2020
@MoonkiHong
Copy link
Contributor Author

@suresh-lc @mgjeong @Karthikeyan-Samsung This is WIP. Please do not review this PR unless I will notify that I am ready to go.. Sorry for disturbing you though...

@MoonkiHong
Copy link
Contributor Author

@tdrozdovsky I would like to suggest to close this PR (without merge), since the current code is not an issue as it is. As we discussed, we can still track this topic from #157 and are able to apply the right PR based on a concrete policy. Thought?

@tdrozdovsky
Copy link
Contributor

@MoonkiHong I agree with you. You can close this PR until the exact policy is clarified

@MoonkiHong MoonkiHong closed this Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Copyright statement] Revoke the PR #157 for the copyright statement correction
2 participants