diff options
author | Peter Todd <pete@petertodd.org> | 2016-10-13 19:31:52 +0200 |
---|---|---|
committer | Peter Todd <pete@petertodd.org> | 2016-10-13 19:47:43 +0200 |
commit | 36f60a5d5b1bc9a12b87d6475e3245b8236775e4 (patch) | |
tree | 1cdb1262d476d1bf3984191b0324091914342302 /src | |
parent | e2b8c394d61de1e153b9b39d99c45654774f00de (diff) | |
download | bitcoin-36f60a5d5b1bc9a12b87d6475e3245b8236775e4.tar.xz |
Add copyright/patent issues to possible NACK reasons
Adding in response to a Slack discussion where someone was unclear on the fact
that a NACK may be justified if code can't be accepted due to copyright/patent
issues. For example, it would be reasonable and prudent to NACK a contribution
of AGPL-licensed consensus code on the basis that the license terms are
incompatible with the MIT license used by the rest of the codebase.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions