这似乎意味着唯一的要求是将许可证文件与代码的“大量”部分放在一起。 但它不应该覆盖 GPL，因为 GPL 的语言更严格并且要求 MIT 部分成为 GPL（在您的版本中）。 换句话说，你的整个软件必须是 GPL。
If you mix code it must comply with both licenses, which generally means they must be compatible. I believe MIT is pretty easy to merge with GPL as long as you obey the following:
The MIT License
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
Which seems to imply the only requirement is to place the license file with an "substantial" portions of code. It should NOT override the GPL though because the language of GPL is more strict and requires the MIT portions to become GPL (in your version). In other words your whole software must be GPL.
发布评论
评论（1）
如果您混合代码，它必须符合两个许可证，这通常意味着它们必须兼容。 我相信只要遵守以下规则，MIT 很容易与 GPL 合并：
这似乎意味着唯一的要求是将许可证文件与代码的“大量”部分放在一起。 但它不应该覆盖 GPL，因为 GPL 的语言更严格并且要求 MIT 部分成为 GPL（在您的版本中）。 换句话说，你的整个软件必须是 GPL。
If you mix code it must comply with both licenses, which generally means they must be compatible. I believe MIT is pretty easy to merge with GPL as long as you obey the following:
Which seems to imply the only requirement is to place the license file with an "substantial" portions of code. It should NOT override the GPL though because the language of GPL is more strict and requires the MIT portions to become GPL (in your version). In other words your whole software must be GPL.