Table of contents
Combined revision comparison
...
When you intentionally send a patch to us by the GitHub pull request function, we regard that you permitted to merge it into our SoftEther VPN source-code tree. Since the entire SoftEther VPN source code is licensed under the Apache License 2.0GPLv2 license, your patch will be also treated to adopt the Apache License 2.0GPLv2 license.
As the consequence, anyone will be permitted to copy, modify or re-use your patch program under the Apache License 2.0GPLv2 license.
...
Version from 11:20, 21 Jan 2019
...
When you intentionally send a patch to us by the GitHub pull request function, we regard that you permitted to merge it into our SoftEther VPN source-code tree. Since the entire SoftEther VPN source code is licensed under the GPLv2 license, your patch will be also treated to adopt the GPLv2 license.
As the consequence, anyone will be permitted to copy, modify or re-use your patch program under the GPLv2 license.
...
Current version
...
When you intentionally send a patch to us by the GitHub pull request function, we regard that you permitted to merge it into our SoftEther VPN source-code tree. Since the entire SoftEther VPN source code is licensed under the Apache License 2.0 license, your patch will be also treated to adopt the Apache License 2.0 license.
As the consequence, anyone will be permitted to copy, modify or re-use your patch program under the Apache License 2.0 license.
...
