On 31/12/2013 04:00, NAKAMURA Takumi wrote:
I will apply them tomorrow.
Hi Takumi,
It's my understanding that copyright is only extended after non-trivial
changes are made to a greater work, so it's more correct to do this a
week or two into 2014 for the most active LLVM modules.
For less active modules like Dragonegg it should not happen before
someone makes an actual code commit.
This isn't a review or legal advice, but a summary of the established
practice I've seen in commercial software.
A quick search suggests the same procedure is used in open software like
GNU:
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html [6.5p8]
Alp.
What should I do else?
- AutoRegen.sh
- ...and?
http://llvm-reviews.chandlerc.com/D2492
Files:
clang-tools-extra/LICENSE.TXT
clang-tools-extra/docs/conf.py
clang/LICENSE.TXT
clang/docs/analyzer/conf.py
clang/docs/conf.py
compiler-rt/LICENSE.TXT
libclc/LICENSE.TXT
libcxx/LICENSE.TXT
libcxxabi/LICENSE.TXT
lld/LICENSE.TXT
lld/docs/conf.py
llvm/LICENSE.TXT
llvm/autoconf/configure.ac
llvm/docs/conf.py
llvm/docs/doxygen.footer
polly/LICENSE.txt
polly/tools/GPURuntime/LICENSE.TXT
_______________________________________________
llvm-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
--
http://www.nuanti.com
the browser experts
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
