You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by home4slc <gi...@git.apache.org> on 2016/10/07 19:43:37 UTC
[GitHub] incubator-edgent pull request #214: EDGENT-262 console license changes
GitHub user home4slc opened a pull request:
https://github.com/apache/incubator-edgent/pull/214
EDGENT-262 console license changes
I added a console/servlets/LICENSE file containing the following:
This initial line of text:
"This product contains content covered by MIT/BSD-3-Clause licenses."
then where the ext files came from, and their associated license type, a URL to the license or path in the repository to the license, and added a couple of license.
I also updated <repo>/LICENSE to mention the console/servlets/LICENSE file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/home4slc/incubator-edgent EDGENT-262_console_licenses
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-edgent/pull/214.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #214
----
commit 8a7bb916b32881f2517ec3f2b36870a630fa01b1
Author: Susan L. Cline <ho...@apache.org>
Date: 2016-10-07T19:38:56Z
EDGENT-262 console license changes
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-edgent pull request #214: EDGENT-262 console license changes
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-edgent/pull/214
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---